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
Is your feature request related to a problem? Please describe
Config option overload.
Describe the feature you'd like to see implemented
multi_json is a popular gem (that we'd need to depend on) for automatically choosing the fastest JSON renderer your application or library has available:
MultiJson.dump({:abc=>'def'})
I've used other serializers, like grape-entity, that support it, as well as many applications. This would simplify configuration by moving it up a layer outside of our library. We could still offer an override for rare cases if we want, maybe via an extension hook.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
IMO, the library shouldn't have a favourite. Extensions should be the way to go ahead for people wanting that extra performance. For majority of the users, the native JSON lib should suffice.
If we dislike the idea of adding a dependency, we could change the above so that the multi_json behavior is available as a built-in, optional V2 extension. That way the application is responsible for handling that dependency.
Is there an existing issue for this?
Is your feature request related to a problem? Please describe
Config option overload.
Describe the feature you'd like to see implemented
multi_json is a popular gem (that we'd need to depend on) for automatically choosing the fastest JSON renderer your application or library has available:
I've used other serializers, like
grape-entity
, that support it, as well as many applications. This would simplify configuration by moving it up a layer outside of our library. We could still offer an override for rare cases if we want, maybe via an extension hook.Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: