feat: Custom Json Serializable Parser for Specific Field Types #424
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why
Sometimes backend can send response that not match specified schema (e.g. expected value is
20, actual is"20"or20.0) and then generator will throw an exception.Solution
json_serializablemakes it possible to specify a custom parser for specific fields, but it requires to indicate such fields with an annotation. However this way supposes manual edit and therefore not quite suitable for generated models.Solution here is to provide opportunity to specify parser per field type in generator configuration.
swagger_parser.yaml:package:your_package/lib/utils/parsers/custom_nullable_int_parser.dart:Result after codegeneration:
some_model.dart: