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

Deserializing absolute paths should not requires a type #45

Open
mixonic opened this issue Nov 24, 2017 · 0 comments
Open

Deserializing absolute paths should not requires a type #45

mixonic opened this issue Nov 24, 2017 · 0 comments

Comments

@mixonic
Copy link
Member

mixonic commented Nov 24, 2017

For example deserializeSpecifier('/some-namespace/') currently returns type === '/some-namespace/'. The leading / should be enough to inform the parser we are providing the path part of the specifier string and not a type.

This is implying a rule: "No type can start with a slash" which I think is pretty reasonable.

/cc @iezer

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

No branches or pull requests

1 participant