I'm here due to the link from RubyWeekly. I haven't watched the video, only seen the notes, but as an ActiveModelSerializers maintainer, I'd ask if the various unusual decisions could be explained and if they should be something the library should handle. For example: 1) mixing in the url helpers is not necessary 2) the show method in the serializer, besides violating separation of concerns, is very strange, and I'm not sure how it would be used 3) code is missing any configuration
1. I tried omitting the URL Helpers on the --api version and ran into undefined method issues. Also, the default_url_options also failed without the url helpers.
2. This definitely would be a very specific use case. It was more of an illustration that ASM does support rendering partials.
I'm here due to the link from RubyWeekly. I haven't watched the video, only seen the notes, but as an ActiveModelSerializers maintainer, I'd ask if the various unusual decisions could be explained and if they should be something the library should handle. For example: 1) mixing in the url helpers is not necessary 2) the show method in the serializer, besides violating separation of concerns, is very strange, and I'm not sure how it would be used 3) code is missing any configuration
Thanks for your work with the gem!
1. I tried omitting the URL Helpers on the --api version and ran into undefined method issues. Also, the default_url_options also failed without the url helpers.
2. This definitely would be a very specific use case. It was more of an illustration that ASM does support rendering partials.
3. Not sure I follow.