On 5/8/13 6:01 AM, Michał Gołębiowski wrote:
> Well, the most elegant way would be IMHO to expand the @sourceMappingURL syntax to be able to provide the source file name or even do some basic string operations on it. I understand such a solution would be a problem considering the aim is to have many implementations of reading the source map path so such complications would hamper the adoption speed. Am I right that's the main problem?
This sounds like over engineering to me.
In my mind, the whole implicit naming structure would exist for the
"plug and play" use case for when you want source maps to Just Work (tm)
and if you need anything more complicated, you are free to specify an
exact URL as we do currently.
What am I missing?