fix(15303): Ensure that all defaults for the forms come from the OpenAPI schemas #16
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.
See https://hivemq.kanbanize.com/ctrl_board/57/cards/15303/details/
This PR changes all the React-Hook-Form forms in the web app (Bridge and Universal Names, Protocol being handled differently) so that their default values are exclusively coming from the OpenAPI specs. For example:
clientId: { type: 'string', description: `The client identifier associated the the MQTT connection.`, isNullable: true, format: 'string', maxLength: 65535, pattern: '([a-zA-Z_0-9\\-])*', },
The changes also imposed the standardisation of the error messages, for example:
Note that, as of v0.25.0, openapi-typescript-codegen used to generate the OpenAPI stubs still mishandles default values set to 0. See ferdikoomen/openapi-typescript-codegen#1558