Feat/appview routing - #36
Open
Ashex wants to merge 2 commits into
Open
Conversation
|
hilkeros
approved these changes
May 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rather then setting a default appview, we're going to take it a little further by introduce a routing function:
What this does, it matched by the PDS/entryway set during login and sets the Appview for the session. This allows us to enforce which appview a user goes to so we don't end up overloading an appview when everyone decides to use the social app and helps maintain a cohesive experience for communities built around a pds/appview.
If a person signs in with a PDS that doesn't match then it will go to the configured fallback.