Unleash / unleash / 24122401223

87%

master: 91%

push

github

chore(AI): projectContextFields flag cleanup (#11706)

This PR cleans up the projectContextFields flag. These changes were
automatically generated by AI and should be reviewed carefully.

Fixes #11705

## 🧹 AI Flag Cleanup Summary
Cleaned up the `projectContextFields` feature flag across the frontend
and
backend codebase as the feature has been kept.
### 🚮 Removed
- **Conditionals**
- Removed logic paths that fell back to the old behavior in frontend
components (`PlaygroundCodeFieldset`, `EditableConstraint`,
`ProjectSettings`).
- Removed API `context` controller branching and fallback fetching
logic.
- Dropped experimental configuration setup from end-to-end tests
(`project-context.e2e.test.ts`,
`context-api-include-query-params.e2e.test.ts`).
- **Configuration**
- Removed `projectContextFields` from backend experimental options in
`src/server-dev.ts` and `src/lib/types/experimental.ts`.
- Removed `projectContextFields` from UI flags config
(`frontend/src/interfaces/uiConfig.ts`).
### 🛠 Kept
- **Logic paths**
- Project level context field routes, fetching `uriFromQuery(query)`
correctly
for hooks.
- Logic parsing grouped context options inside
`createContextFieldOptions`.
- Metrics tracking on `projectContextFieldCount`.
### 📝 Why
The `projectContextFields` flag is permanently integrated into the core
product,
meaning project-level context fields are now a stable feature.
Therefore, all
conditions preventing access to it (and the associated definitions in
test
environments / configs) were safely deleted to tidy up the codebase.

---------

Co-authored-by: unleash-bot <194219037+unleash-bot[bot]@users.noreply.github.com>
Co-authored-by: Thomas Heartman <thomas@getunleash.io>

1818 of 2010 branches covered (90.45%)

2 of 2 new or added lines in 2 files covered. (100.0%)

14975 of 17191 relevant lines covered (87.11%)

940.47 hits per line