feat: add useProperSingularization option for model name singularization - #440
Conversation
ballistic-booger
commented
Jul 27, 2026
- 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
Release Assistant - PassedAll requirements satisfied. Release Information:
This PR is ready to merge. |
|
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
|
Yes, you can't add labels from outside the repo... I didn't know about this limitation. I'll simply add the labels to PR's don't worry about it |
- Revert changes made to the README.