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

Migration from AMS #137

Open
lucashungaro opened this issue Apr 30, 2023 · 2 comments
Open

Migration from AMS #137

lucashungaro opened this issue Apr 30, 2023 · 2 comments

Comments

@lucashungaro
Copy link

Hi! Sorry about opening an issue, I tried to find other forms of contact but it appears the links to the Slack community are broken.

I have a large project using AMS that should benefit a lot from more efficient serializers. Is Panko a drop-in replacement for AMS at this point? Is there a migration guide of any sort? I'm trying to gauge/estimate the work to migrate and that would greatly help me.

If I had a simple list of what works and what doesn't I could just go the "install Panko, replace AMS references, replace non-compatible methods, and run the specs" route. :)

Thank you!

@yosiat
Copy link
Owner

yosiat commented Apr 30, 2023

Hi @lucashungaro

The migration is not a drop-in replacement, actually in a repo I have at work we use both AMS and Panko and do serializer-by-serializer migration, since there are breaking changes - the use of Panko::Response and other-features.

@lucashungaro
Copy link
Author

Hi @yosiat, thanks for the response!

So that would be the ideal migration process? Install them side by side and slowly migrate? It there any simple way to know which features from AMS this gem doesn't cover?

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