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
What is your use-case and why do you need this feature?
For the JSON format, do validation during deserialization is absolutely effecienct. Are there any plan or suggestion to complete it?
The text was updated successfully, but these errors were encountered:
Can you elaborate, please? We do not have any integrations with Json Schema for now, any kind of advanced validation should happen in init {} block of serializable classes
Thank you, I means if we can add some feature for it, compose the decoding and validation process, it will be more effeciency. Such as we needn't tokenize the input again.
In that case, JSON schema is a good choice, because it's standardized and widely supported.
I still don't get how it should look like. And what do you mean by 'needn't tokenize the input again.'? If you have your validation in init{}, it happens after the class is deserialized as usual.
I understand we can do validation during class init, but here's a problem that it's not standardized and it can't cross platform.(I means programming language.).
What is your use-case and why do you need this feature?
For the JSON format, do validation during deserialization is absolutely effecienct. Are there any plan or suggestion to complete it?
The text was updated successfully, but these errors were encountered: