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
Just an idea for myself for potential mapping for versioning:
Currently, mapping is defined using Resource and Collection annotations:
/** * @REST\Resource(controller="MyController") * @REST\Collection(controller="MyCollectionController") */ class Resource
The idea is to simply add a "mediaVersion" parameter that would be used during content negotiation:
/** * @REST\Resource(mediaVersion="application/vnd.v1+json", controller="MyController") * @REST\Resource(mediaVersion="application/vnd.v2+json", controller="MyControllerV2") */ class Resource
The text was updated successfully, but these errors were encountered:
@bakura10 still confusing IMO. So you'd support versions only via content negotiation?
Sorry, something went wrong.
I agree, that was a bad idea. As you said, if we should support versioning it should be a complete cloning of the project inside a new namespace.
No branches or pull requests
Just an idea for myself for potential mapping for versioning:
Currently, mapping is defined using Resource and Collection annotations:
The idea is to simply add a "mediaVersion" parameter that would be used during content negotiation:
The text was updated successfully, but these errors were encountered: