We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Url aggregator is the mostly used parser. Let us consider dropping url for the next major and maybe calling it url?
This would simplify codebase a lot and make our jobs easier for can parse, as well as urlpattern?
The text was updated successfully, but these errors were encountered:
cc @lemire what do you think?
Sorry, something went wrong.
@anonrig Hmmm... We should always have some care before introducing a breaking change.
How sure are we that there is no user? If we can be certain that nobody uses it, then I am all for pruning it.
But let us not break people's code without warning !!!
Strongly recommend taking things through a proper deprecation cycle on stuff like this.
Which deprecation cycle do you recommend we follow? I think first we need to document that.
This goes a bit against my proposal to use the fact that we have two functionally equivalent implementations to improve testing.
anonrig
No branches or pull requests
Url aggregator is the mostly used parser. Let us consider dropping url for the next major and maybe calling it url?
This would simplify codebase a lot and make our jobs easier for can parse, as well as urlpattern?
The text was updated successfully, but these errors were encountered: