-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Additional APIs #30
Comments
Yes. I'd like to discuss that! Would you be open to creating 3 separate PRs / issues? At the very least, I can give architectural context/guidance for each of them. |
Nice pr in #31 @kortirso! I'll take a look later this week. I feel like that one might take a bit more time for me to review. If you are open to PRing for Also as you're migrating from |
@jho406 what is better approach for formatting keys?
|
The latter.
Do it directly. Its a low effort approach, speedy, and if you plan to use it in JS land, easier to search for. |
@kortirso Thanks for the PRs! Sorry it took a while. How the integration with |
While we were integrating props into our application, we added some additional APIs that were spied on by the Jbuilder.
json.optional!
- defines attribute or structure and marks it as optional, during serialization this method checks condition and renders or does not render such attributeexample of usage
json.extract!
- extracts the mentioned attributes or hash elements from the passed object and turns them into attributes of the JSONexample of usage -
json.extract! object, :id, :unit
instead of
json.partial!
- renders partial without setting result to some key@jho406 do you have any plans to integrate such features to PropsTemplate? Or maybe I can share their implementation and then dicsuss/modify/accept/reject them, what do you think?
The text was updated successfully, but these errors were encountered: