Bugfix/required and nullable difference

[domenikjones]

Hi there,

We have found a problem concerning nullable fields which lead into more problems, if we are using required, readOnly and nullabel in combination.

To keep the possibility as before, strictRequiredChecks has been added.

• strictRequiredChecks will allow undefined values
• strictNullChecks will allow null values

We have implemented some changes:

• Extend the field props with the values for nullable and readOnly
• Changed the behavior of a field description based on these values (for undefined and null seperately)

A field is required when:

• The field property readOnly is false and property is required is true or strictRequiredChecks is false

A field is nullable when:

• The field property nullable is true or strictNullChecks is false

These changes might break implementations of other developers, since strictNullCheck has been moved to the nullable evaluation instead required aka undefined.

Please let me know this poses a problem. Happy coding!

[domenikjones]

Will do more changes..

[Manweill]

In current version, more is to compatibility with JS developers, and their backend service provided OpenAPI does not fully describe the input and output parameters of the entire api. they are tightly used to call the request api. Welcome to communicate with me more ideas