Skip to content

feat: add useProperSingularization option for model name singularization#440

Open
ballistic-booger wants to merge 1 commit into
DaredevilOSS:mainfrom
ballistic-booger:fix-singularization-logic
Open

feat: add useProperSingularization option for model name singularization#440
ballistic-booger wants to merge 1 commit into
DaredevilOSS:mainfrom
ballistic-booger:fix-singularization-logic

Conversation

@ballistic-booger

Copy link
Copy Markdown
Contributor
  • add rule-based Singularize to StringExtensions (policies -> Policy, statuses -> Status, devices -> Device)
  • thread new opt-in flag through ToModelName callers in DataClassesGen, ModelsGen, CommonGen, DbDriver, EnumDbDriver
  • expose useProperSingularization in RawOptions/Options, default false to keep legacy TrimEnd('s') behavior
  • add ModelNameTests covering both legacy and proper singularization paths
  • document the option in README and docs/03_Usage.md
  • regenerate example request.json/request.message fixtures with the new option field

- add rule-based Singularize to StringExtensions (policies -> Policy, statuses -> Status, devices -> Device)
- thread new opt-in flag through ToModelName callers in DataClassesGen, ModelsGen, CommonGen, DbDriver, EnumDbDriver
- expose useProperSingularization in RawOptions/Options, default false to keep legacy TrimEnd('s') behavior
- add ModelNameTests covering both legacy and proper singularization paths
- document the option in README and docs/03_Usage.md
- regenerate example request.json/request.message fixtures with the new option field
@github-actions

Copy link
Copy Markdown
Contributor

Release Assistant - Action Required

Version-worthy changes detected in:

  • CodeGenerator/
  • Drivers/
  • Extensions/
  • PluginOptions/

Add one of the following labels to this PR: major, minor, patch.

  • patch — Bug fixes, documentation updates
  • minor — New features, backwards-compatible
  • major — Breaking changes, API modifications

This PR cannot be merged until a version label is added.

@ballistic-booger

Copy link
Copy Markdown
Contributor Author

Not sure what the release-assistant/requirements failure is referring to, when I open it up it looks like it passed.

@doron050

Copy link
Copy Markdown
Collaborator

Not sure what the release-assistant/requirements failure is referring to, when I open it up it looks like it passed.

It refers to this #440 (comment)

I added it so the release process will be easier

Tldr - add a label to the PR that represents your change type and this will be calculated into the next release version

@ballistic-booger

ballistic-booger commented Jul 27, 2026

Copy link
Copy Markdown
Contributor Author

Not sure what the release-assistant/requirements failure is referring to, when I open it up it looks like it passed.

It refers to this #440 (comment)

I added it so the release process will be easier

Tldr - add a label to the PR that represents your change type and this will be calculated into the next release version

Thanks for clarifying. I tried to add the label, but it seems like I don't have the permissions to do so. Neither the UI or gh let's me.

❯ gh pr edit 440 --repo DaredevilOSS/sqlc-gen-csharp --add-label minor
GraphQL: ballistic-booger does not have the correct permissions to execute AddLabelsToLabelable (addLabelsToLabelable)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants