ui.publicPages
should bypass ui.isAccessAllowed
and ui.pageMiddleware
#8120
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.
I think the previous behaviour was unintentionally misleading; and although #8115 resolved the behaviour as near to what existed before, I don't think this what developers are expecting.
Public pages shouldn't be redirected conditionally in respect to the session, they are public pages.
If they can be conditionally re-directed as a result of
ui.isAccessAllowed
or some other behaviour, then they aren't public pages, but conditional pages, and can be handled usingui.pageMiddleware
.This pull request resolves that ambiguity as a separate followup to #8115.
This pull request additionally restores a small optimization that we had which prevented
hasInitFirstItemConditions
calling the database for every request if asession
already exists (and thereby, initialization already completed).