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
Wondering if there are plans (or it is already implemented but im doing it wrong) for blacklist and whitelist rules to apply to deserialize. Currently it seems to be outputting a deserialized version of the data regardless of these rules. I am having to deserialize, serialize and then deserialize to get the clean data.
The text was updated successfully, but these errors were encountered:
@hilaryosborne Your are right, currently blacklist or whitelist options are only effective on serialization.
I think we can't apply these same options on deserialization. because attributes to remove or keep when serialize or deserialize can be different.
We need a blacklist and a whitelist options on deserialization too. I suggest to add these 2 options :
blacklistOnDeserialize
whitelistOnDeserialize
Maybe you have a better idea for naming these options ?
Wondering if there are plans (or it is already implemented but im doing it wrong) for blacklist and whitelist rules to apply to deserialize. Currently it seems to be outputting a deserialized version of the data regardless of these rules. I am having to deserialize, serialize and then deserialize to get the clean data.
The text was updated successfully, but these errors were encountered: