You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 6, 2020. It is now read-only.
I'm curious what might a strategy for versioning an API with Seahorse look like? If there are any unique ways that Seahorse can potentially help with that or a more traditional Rails approach of duplicating models and specs is needed.
The text was updated successfully, but these errors were encountered:
I think the best approach is to duplicate the models and version them this way.
Then you can use every version of the api with the different JSON description.
But as I've seen, there is currently nothing in there at the moment.
In @trevorrowe's talk, he spoke about duplicating the models as @Neonlex suggested and tracking them individually via git. This also allows you to host and route both APIs independently in your application at the same time. There's certainly more to be learned in this area though. The best would be to see what strategies users are having success with in the wild and applying those solutions into Seahorse.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm curious what might a strategy for versioning an API with Seahorse look like? If there are any unique ways that Seahorse can potentially help with that or a more traditional Rails approach of duplicating models and specs is needed.
The text was updated successfully, but these errors were encountered: