Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Will name resolution dictate forward slashes? #39

Open
johnjbarton opened this issue Mar 22, 2015 · 2 comments
Open

Will name resolution dictate forward slashes? #39

johnjbarton opened this issue Mar 22, 2015 · 2 comments

Comments

@johnjbarton
Copy link

As far as I can gather, the current consensus is for module keys to be absolute URLs. Ignoring the issue of URLs vs module identifiers, is there at least agreement that the paths are separated by forward slashes?

@caridy
Copy link
Contributor

caridy commented Mar 23, 2015

why will that matter? In theory those are internal operations, and the loader can probably rely on the runtime configuration.

@johnjbarton
Copy link
Author

For dynamic loading, developers will want to rely on string manipulation libraries for constructing module specifiers. In tools that iterate over the loaded modules, the keys will need to be converted into values that can be fetched. Of course the internal format of the keys should not be part of the spec, but the API should dictate the form of module specifiers, any other inputs to the names, and the format of keys coming back out. Specifying forward slashes would be a great help to developers with almost no cost and few downsides in practice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants