ignoreNullMembers Annotation is ignored about dart-json-mapper

[Lars-Sommer]

I´ve tried what you suggested, and it works.
So the problem is that when you add annotation options, the builder doesn´t care about them until the @JsonSerializable() is removed from the class and added again?
Anyways, thanks alot!

By the way, it would be nice if you could call initializeJsonMapper() with some default options, like ignoreNullMembers - but that is a detail. Thanks alot for an awesome project, it´s a great help!

[k-paxian]

As far as I can see, you cannot set default annotations like this, for all classes, is that correct?

yep, for global context you have SerializationOptions, for local context individual annotations.

I'll check this case and let you know what's wrong with it. Seems legit case for me

[k-paxian]

Well, here is a unit test which is covering this functionality.

dart-json-mapper/perf-test/test/unit/test.constructors.dart

Line 394 in 6d8da09

test('IgnoreNullMembers class', () {

and it's green 💚
Highly probably you've not regenerated the code after altering @Json(ignoreNullMembers: true) annotation.

To force full regeneration cycle, you can:

• comment out any @JsonSerializable() annotation, switch your keyboard focus on the console running build runner
• wait till build runner finishes it's pass
• un-comment @JsonSerializable() annotation back and wait till build runner will succeeds

Usually to save on coding performance, code is not fully regenerated while you are typing. The only thing sensible is the presence/absence of @JsonSerializable() / @jsonSerializable annotation

[k-paxian]

Thanks for the suggestion, makes sense to me. I'll take it as improvement 😉

[Lars-Sommer]

Cool 🍻😊

[k-paxian]

@fasterlars Since 2.2.6+1 initializeJsonMapper() accepts global serialization/deserialization options. That's actually saved me a lot of redundant code in unit tests well done 👍 through the years I've not noticed such a straight forward move 😄

[Lars-Sommer]

Haha, awesome! 👍