[GR-41981] Use canonical resource path in resource registration #9577
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.
This PR adds support for registering resources requested with a non-canonical path. This could happen when:
getResource
orgetResourceAsStream
for example) with a non-canonical path (e.g.foo/../test.txt
should be justtest.txt
)Note: if a resource comes from a jar and it is requested with a non-canonical path, we should return
null
in order to have the same behavior as Java (and our current implementation does that)