Cleaning up the checks in Modules renderer for performance #6032
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.
See #5996. This shuffles around the checks in the modules renderer to bail out as soon as possible for the module editing. The only functional change is, that module editing with this requires that the user is logged in regardless of the permissions set. The situation that an unauthenticated user is allowed to edit modules in the frontend, is VERY uncommon.
How to test
Make sure that you are not logged in when doing this. There should be no change in performance if the user is logged in.