Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[kotlin] Enum should match spec #18062

Merged
merged 5 commits into from Mar 9, 2024
Merged

[kotlin] Enum should match spec #18062

merged 5 commits into from Mar 9, 2024

Conversation

wing328
Copy link
Member

@wing328 wing328 commented Mar 9, 2024

based on #16333, #17387

  • Adjust the enum generation to match what is in the spec, rather than camel-casing it.
  • Regenerate docs

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.1.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.

@jimschubert
@dr4ke616
@karismann
@Zomzog
@andrewemery
@4brunu
@yutaka0m
@stefankoppier

snowe2010 and others added 5 commits February 1, 2024 13:15
Adjust the enum generation to match what is in the spec, rather than
camel-casing it.
Add tests for capitalization scenarios, including for kotlin keywords
@wing328 wing328 changed the title Jarin issue/3804b [kotlin] Enum should match spec Mar 9, 2024
@wing328 wing328 added this to the 7.4.0 milestone Mar 9, 2024
@wing328 wing328 marked this pull request as ready for review March 9, 2024 09:42
@wing328 wing328 merged commit 494fc7d into master Mar 9, 2024
63 checks passed
@wing328 wing328 deleted the jarin-issue/3804b branch March 9, 2024 09:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants