Fix validation constraints for parameters in request body of form request are not generated (at least with Spring Boot generator)

[oliverkuntze]

@cachescrubber @welshm @MelleD @atextor @manedev79 @javisst @borsch @Zomzog @martin-mfg

Validation constraints like minLength, maxLength, pattern defined for parameters within request bodies of
application/x-www-form-urlencoded content are not generated in the API interfaces.

The formParams.mustache is missing the beanValidationBodyParams template call (as opposed for example to the regular bodyParams.mustache).

This PR fixes it for the Spring generator.

PR checklist

• Read the contribution guidelines.
• Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community.
• Run the following to build the project and update samples:

  ./mvnw clean package || exit
  ./bin/generate-samples.sh ./bin/configs/*.yaml || exit
  ./bin/utils/export_docs_generators.sh || exit
  

  (For Windows users, please run the script in WSL)
  Commit all changed files.
  This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
  These must match the expectations made by your contribution.
  You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example ./bin/generate-samples.sh bin/configs/java*.
  IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
• File the PR against the correct branch: master (upcoming 7.x.0 minor release - breaking changes with fallbacks), 8.0.x (breaking changes without fallbacks)
• If your PR solves a reported issue, reference it using GitHub's linking syntax (e.g., having "fixes #123" present in the PR description)
• If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.

[wing328]

Thanks for the PR but your commit (as shown in the Commits tab) is not linked to your Github account, which means this PR won't count as your contribution in https://github.com/OpenAPITools/openapi-generator/graphs/contributors.

Let me know if you need help fixing it.

Ref: https://github.com/OpenAPITools/openapi-generator/wiki/FAQ#how-can-i-update-commits-that-are-not-linked-to-my-github-account

[wing328]

https://github.com/OpenAPITools/openapi-generator/actions/runs/16968373859/job/48211714077?pr=21749

please follow step 3 to update the samples

https://github.com/OpenAPITools/openapi-generator/actions/runs/16968373866/job/48211619581?pr=21749

that's fixed in the latest master. please merge it into your branch

thanks for the contribution

[oliverkuntze]

Thanks for the PR but your commit (as shown in the Commits tab) is not linked to your Github account, which means this PR won't count as your contribution in https://github.com/OpenAPITools/openapi-generator/graphs/contributors.

Let me know if you need help fixing it.

Ref: https://github.com/OpenAPITools/openapi-generator/wiki/FAQ#how-can-i-update-commits-that-are-not-linked-to-my-github-account

Thanks for the hint! Fixed.

[oliverkuntze]

https://github.com/OpenAPITools/openapi-generator/actions/runs/16968373859/job/48211714077?pr=21749

please follow step 3 to update the samples

https://github.com/OpenAPITools/openapi-generator/actions/runs/16968373866/job/48211619581?pr=21749

that's fixed in the latest master. please merge it into your branch

thanks for the contribution

I merged the latest master into my branch.

Added the samples that were created during the bin/generate-samples.sh run.

[oliverkuntze]

@wing328 Do you have any idea when the pr could be merged? :-)

[wing328]

just merged it.

thanks for the contribution.

have a nice weekend.

[oliverkuntze]

Great! Thanks a lot!
Have a nice weekend, too.