Thanks@kschwab

Is it a fix for an issue?

@hramezani yes, it is an issue I found locally. I can open a formal ticket if you would like.

CliApp.serialize is incorrect whencli_kebab_case is enabled. Currently on main it will do the below:

frompydantic_settingsimportBaseSettings,CliAppclassCfg(BaseSettings,cli_kebab_case=True):foo_kebab:int=123args=CliApp.serialize(Cfg())print(args)#> ['--foo_kebab', '123']CliApp.run(Cfg,cli_args=args)"""usage: example.py [-h] [--foo-kebab int]example.py: error: unrecognized arguments: --foo_kebab 123"""

With this fix, it will correctly apply the kebab case to serialization:

frompydantic_settingsimportBaseSettings,CliAppclassCfg(BaseSettings,cli_kebab_case=True):foo_kebab:int=123print(CliApp.serialize(Cfg()))#> ['--foo-kebab', '123']print(CliApp.run(Cfg,cli_args=args))#> foo_kebab=123

I also missed serialization of subcommands, which addressed as well in this PR. See addedtest.

I also just noticed thatcli_implicit_flags case will also likely need an adjustment.

Ok@hramezani, this is ready for review again. When I looked closer, there were a handful of bugs I found with the original serialization. The change set looks larger then it is. Ireverted the original serialization implementation, and consolidated it into two standalone functions.

The bugs I found and fixed were:

• Serializationordering could be wrong. i.e., ordering of positionals and subcommands has to be strictly maintained.
• Skip serialization ofdefaults. Only modified values should be serialized.
• Handle serialization ofkebab case.
• Handleimplicit bool flags.

All the newly added tests currently fail on main.