You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Update document and working example on flag parsing #563
The code lab now documents DEFINE_fiddle_config() and DEFINE_fiddle_sweep() and explicitly labels fiddle/absl_flags/example as the legacy example. The modern single-config example is still under _src.
I checked current main (8384c49d6fc7895dadd220e11dc7e7bb02129890): a fiddler returning a replacement config leaves the legacy result unchanged, while the modern API uses the replacement. The documented legacy example itself runs successfully, and the 23 flag-utility/sweep tests pass.
Is the remaining scope here a public runnable modern-API example alongside the legacy one, or do you want the existing business example migrated? Adding a modern sibling would let it demonstrate immutable fiddlers while preserving the documented legacy commands.
Activity
rksharma-owg commentedon Oct 14, 2026
The code lab now documents
DEFINE_fiddle_config()andDEFINE_fiddle_sweep()and explicitly labelsfiddle/absl_flags/exampleas the legacy example. The modern single-config example is still under_src.I checked current main (
8384c49d6fc7895dadd220e11dc7e7bb02129890): a fiddler returning a replacement config leaves the legacy result unchanged, while the modern API uses the replacement. The documented legacy example itself runs successfully, and the 23 flag-utility/sweep tests pass.Is the remaining scope here a public runnable modern-API example alongside the legacy one, or do you want the existing business example migrated? Adding a modern sibling would let it demonstrate immutable fiddlers while preserving the documented legacy commands.