Consistently resolve component resources using relative paths #3303
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.
Followup for #3284
This PR cleans up some of the crufty bits that were in the original
ComponentResourceHandler
PR. Specifically all URLs for custom component resources are now expressed relative to the component. This means we are no longer encoding absolute paths in the URL (and indeed we no longer accept absolute paths either). Additionally this cleans up the code a bit ensuring that everywhere that generates and consumes component URLs uses the same functions to do so.