REPOSITORY CODING · MEDIUM
Merge relative paths with the base directory, replacing its final file segment
Merge relative paths with the base directory, replacing its final file segment. Authority with an empty base path supplies a leading slash. The complete application includes native models, services, repository projections, a working preview and visible acceptance cases. Preserve the other documented invariants and run bash test/run.sh.
uri-referenceHierarchical URI resolution laboratory
Work through a real codebase.
Choose an environment, investigate the existing implementation and use the tests to check your change. Sign in to open a workspace; execution and Ono usage follow your plan’s allowances.
Task requirements and environments
Java · 55 minute session
- Merge relative paths with the base directory, replacing its final file segment. Authority with an empty base path supplies a leading slash.
- Remove literal dot segments including terminal dot and parent segments while preserving duplicate slashes and percent-encoded dot text.
- An explicitly empty query replaces the base query. An absent query inherits only when the reference path is empty.
- Network-path references replace authority, and fragments always come from the reference. An absent fragment never inherits the base fragment.
- An explicit absolute reference replaces the base scheme and normalizes scheme case. Reject opaque URIs rather than silently treating them as hierarchical.
- RFC 3986 section 5.2 hierarchical subset. Inputs are at most 1024 characters and forty references. Raw encoded path/query/fragment data is preserved; the workbench makes no network requests.
Spring Boot · 55 minute session
- Merge relative paths with the base directory, replacing its final file segment. Authority with an empty base path supplies a leading slash.
- Remove literal dot segments including terminal dot and parent segments while preserving duplicate slashes and percent-encoded dot text.
- An explicitly empty query replaces the base query. An absent query inherits only when the reference path is empty.
- Network-path references replace authority, and fragments always come from the reference. An absent fragment never inherits the base fragment.
- An explicit absolute reference replaces the base scheme and normalizes scheme case. Reject opaque URIs rather than silently treating them as hierarchical.
- RFC 3986 section 5.2 hierarchical subset. Inputs are at most 1024 characters and forty references. Raw encoded path/query/fragment data is preserved; the workbench makes no network requests.