-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Let FlattenJson adapter decide it doesn't include meta #1048
Conversation
👍 |
@joaomdmoura any objections to moving the include_meta unless FlattenJson from the Adapter class to the FlattenJson class? |
|
||
private | ||
|
||
# no-op |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about a more specific comment, nothing big, just to help ppl jumping in the code.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no-op: The FlattenJson adapter does not include meta data
? no-op: The FlattenJson adapter only serializes attributes
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no-op: FlattenJson adapter does not include meta data, because it does not support root.
😄
👍 LGTM, just waiting for the comment before merging. |
8b50d37
to
98d009a
Compare
updated |
Great! I'm merging it. |
Let FlattenJson adapter decide it doesn't include meta
Why should the superclass get to decide it wants to
exclude meta from one of its subclasses. I say don't ask
if we're a FlattenJson adapter, tell the adapter to
include the meta and let FlattenJson no-op on it.
From discussion in #1041