[SID-1577] Restrict access to custom pages #19
Merged
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.
Apply
privatePaths
to custom pages, as well as the docs. Add the configuration option to determine the behaviour in case someone ends up on a private path.Added the
uxMode
config option to define behaviour when an unauthenticated user accesses a private path:redirect
is the default option, behaves consistent to the previous version - redirects to the path defined asprivateRedirectPath
or"/"
modal
will render the login form on top of the private pageTesting
Released a beta version -
@slashid/[email protected]