Currently, if both types of tags are defined on fields, schemas for both formData and json will be create with separate content types. This not a commonly desired outcome as usually only one type is needed, while json can also be defined for other needs.
This PR adds a check to ignore json in such case, also it adds a lebeling interface to restore original behavior for edge cases.
Currently, if both types of tags are defined on fields, schemas for both
formDataandjsonwill be create with separate content types. This not a commonly desired outcome as usually only one type is needed, whilejsoncan also be defined for other needs.This PR adds a check to ignore
jsonin such case, also it adds a lebeling interface to restore original behavior for edge cases.