fix(JSResourceLocator): Consider configured app roots for files #43917
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.
Summary
#40898 introduced an issue when loading scripts from other app roots,
the problem is that the app roots are manually queried and then tried, but if the apps directory path is not a child of the server root the webroot could not be guessed.
The solution I propose is also simplifying the code I think:
Instead of looking into app roots after all other queries we load the app path and app webroot for the requested script in the beginning.
Then we try all paths like before, except for
apps/...
we now use{apppath}/...
directly as this also works for the nativeapps
root.Here we also pass the matching app webroot so we do not need to fallback to the ResourceLocator guessing function.
Checklist