Skip to content

Encourage optional feature flag names that work as startup props#7531

Open
labkey-adam wants to merge 1 commit intodevelopfrom
fb_feature_flag_names
Open

Encourage optional feature flag names that work as startup props#7531
labkey-adam wants to merge 1 commit intodevelopfrom
fb_feature_flag_names

Conversation

@labkey-adam
Copy link
Copy Markdown
Contributor

@labkey-adam labkey-adam commented Mar 28, 2026

Rationale

Optional/experimental feature flags automatically get registered as startup properties, but only if their names conform to Java identifier rules because that what properties files require. We've been logging non-conforming names with the hope that this will encourage developers to use conforming names. It's not working and the logging is just noise on every startup (recently removed for production deployments, but still worthless). Now switching strategy to disallow non-conforming names while grandfathering the existing non-conforming names. (It's a pain to change existing flag names.)

Related Pull Requests

@labkey-adam labkey-adam changed the title Encourage optional feature flag names to work as startup props Encourage optional feature flag names that work as startup props Mar 28, 2026
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.

1 participant