Erlang server validation bugfixes and capability extensions

[NelsonVides]

Three things:

• First of all, fix a bug where exclusiveMinimum and exclusiveMaximum were considered integers, when they are in fact booleans.
• Add support for validating that strings of format byte are indeed base64 encoded and return them parsed.
• Likewise for strings of format date-time.

Other changes are related to general performance optimisations and code quality.

Question, @wing328, I'm not sure to understand how documentation for the capabilities of the generators work, and I'm afraid they might be falling behind with all the recent changes, can you share with me some directions on this? I'd work on that on a follow-up PR though, just to keep this one focused.

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 
  ./bin/generate-samples.sh ./bin/configs/*.yaml
  ./bin/utils/export_docs_generators.sh
  

  (For Windows users, please run the script in Git BASH)
  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 is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.
  • That's myself :)

[wing328]

Question, @wing328, I'm not sure to understand how documentation for the capabilities of the generators work, and I'm afraid they might be falling behind with all the recent changes, can you share with me some directions on this? I'd work on that on a follow-up PR though, just to keep this one focused.

are you referring to updating https://github.com/OpenAPITools/openapi-generator/blob/master/modules/openapi-generator/src/main/java/org/openapitools/codegen/languages/ErlangServerCodegen.java#L50 ?

[wing328]

thanks for the PR

fyi @tsloughter (2017/11) @jfacorro (2018/10) @robertoaloi (2018/10) @NelsonVides (2024/09)