-
-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
the url pattern is not conform to the URI generic syntax in the newest version 3.1.0 #2876
the url pattern is not conform to the URI generic syntax in the newest version 3.1.0 #2876
Comments
The URI syntax refers to https://en.wikipedia.org/wiki/Uniform_Resource_Identifier#Definition |
This was introduced to easily allow some oath services like GitHub as seen in #2125 |
Hello @posva . I work on the wordpress site and on the admin side url to post page looks like this: /wp-admin/post.php?post=123 Can you please advice to me any workaround? Thanks in advance. |
Interesting, I really thought nobody was using that. Since the query can be accessed on server while the hash cannot, I think it makes sense to revert this behavior since you could theorically send different pages from the server with a different query The workaround is for the other issue, not for this one |
In case of wordpress, it's really so, because here everything is a "post": products, orders, news, etc. |
Do you know of wordpress plugins using Vue Router like this? I would like to search a bit more because I'm curious |
I doubt, that my case is widespread, because in general I've seen not a lot of examples of using Vue in wordpress plugins. Thank you for the help! |
I agree parsing the uri in string by ourselves is a work around for this, but following the uri syntax can save a lot time for everyone. |
Version
3.1.0
Reproduction link
https://github.com/yangshuan/vue-router-test-3.1.1
Steps to reproduce
Steps are very simple:
What is expected?
The URI should always be conform to the URI generic syntax 'scheme:[//authority]path[?query][#fragment]', otherwise most of the lib or code which get the parameters from the URI will fail.
What is actually happening?
this url is not conform to the URI generic syntax which is 'scheme:[//authority]path[?query][#fragment]';
The problem the 3.1.0 version brings out is that, when we want to get the parameters from the URL by the default URI generic syntax, we fail all the time, since the uri is not right.
The text was updated successfully, but these errors were encountered: