short circuit depth check if current URL is already sufficient for ResourceInterface.resolveRelativeUrl

[thescientist13]

…race resolveRelativeUrl

Related Issue

N / A

As part of AnalogStudiosRI/www.analogstudios.net#72, noticed that if I had a deep route like
/albums/some-album-name/

Deeply nested paths and relative directories were causing issues, lead to file being loaded like this from the browser

../albums/styles/theme.css

This is more or less what #691 is an open discussion about

This of course can be solved in userland already but requires a conditional with the current ResourceInterface.resolveRelativeUrl because we start slicing and return undefined

const location = this.resolveRelativeUrl(nodeModulesLocation, barePath) || barePath;

However, since the routing will always be dynamic, it would just a bit more ergonomic if resolveRelativeUrl could just help us out regardless of the scenario

const location = this.resolveRelativeUrl(nodeModulesLocation, barePath)

Summary of Changes

1. Make ResourceInterface.resolveRelativeUrl a little more ergonomic by just return the URL if it actually doesn't need to be resolved