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

Support versioning #94

Open
bakura10 opened this issue Oct 26, 2013 · 2 comments
Open

Support versioning #94

bakura10 opened this issue Oct 26, 2013 · 2 comments

Comments

@bakura10
Copy link
Member

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
@Ocramius
Copy link
Member

@bakura10 still confusing IMO. So you'd support versions only via content negotiation?

@bakura10
Copy link
Member Author

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.

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

2 participants