-
Notifications
You must be signed in to change notification settings - Fork 24.7k
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
Use only one way of specifying routing, version and version_type #13377
Labels
:Core/Infra/REST API
REST infrastructure and utilities
>deprecation
good first issue
low hanging fruit
help wanted
adoptme
v6.0.3
Comments
alexksikes
added
discuss
:Core/Infra/REST API
REST infrastructure and utilities
v2.1.0
labels
Sep 7, 2015
jpountz
changed the title
Use only of way of specifying routing, version and version_type
Use only one way of specifying routing, version and version_type
Sep 8, 2015
Please no. :-) +1 on settling on just one |
clintongormley
added
>enhancement
good first issue
low hanging fruit
help wanted
adoptme
v5.0.0-alpha1
and removed
discuss
v2.3.0
labels
Jan 28, 2016
Closed
Let's settle on a single form (I don't really care if it is |
clintongormley
added
>deprecation
v5.0.0-alpha3
and removed
>enhancement
v5.0.0-alpha2
labels
Apr 20, 2016
I was thinking of working on this issues, isn't it already fixed though? #27040 (comment) |
Good catch @mariha it has been addressed indeed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Core/Infra/REST API
REST infrastructure and utilities
>deprecation
good first issue
low hanging fruit
help wanted
adoptme
v6.0.3
Today we have a couple of ways of specifying the routing, version, and version
type of a given document request.
Beyond camelCase, we use:
_routing
orrouting
_version
orversion
_version_type
orversion_type
This makes the use of ParseField difficult for these parameters, as the camelCase of say
_routing
isn'trouting
. We should probably settle on using only one, or make ParseField handle this case.Relates to #8988
The text was updated successfully, but these errors were encountered: