NO-JIRA: Convert useTechPreviewFlagProvider to static function

[logonoff]

(s3e5 "Initiation")

window.SERVER_FLAGS is generated by the backend server and is known to not change. Thus, we do not need a hook and ReactNode for this flag, and we can simplify this to a simple console.flag for performance

Summary by CodeRabbit

• Refactor
  • Restructured tech preview feature flag initialization and registration for improved code maintainability.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[openshift-ci-robot]

@logonoff: This pull request explicitly references no jira issue.

Details

In response to this:

window.SERVER_FLAGS is generated by the backend server and is known to not change. Thus, we do not need a hook and ReactNode for this flag, and we can simplify this to a simple console.flag for performance

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[logonoff]

/label px-approved
/label docs-approved
/assign @TheRealJon @vojtechszocs

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request refactors the tech preview feature flag initialization in OpenShift Console. The change migrates from a hook-based provider pattern (useTechPreviewFlagProvider) to a handler-based pattern. A new tech-preview.ts module exports a FeatureFlagHandler that sets the FLAG_TECH_PREVIEW flag based on window.SERVER_FLAGS.techPreview. The console extensions configuration is updated to reference the new handler, the package.json exports are adjusted to point to the new module, and the legacy hook module is removed. The underlying flag-setting logic remains functionally equivalent.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The PR title accurately describes the main refactoring: converting a React hook (useTechPreviewFlagProvider) into a static function for the tech preview flag.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@frontend/packages/console-app/src/features/tech-preview.ts`:
- Around line 4-5: The current handler sets FLAG_TECH_PREVIEW from
window.SERVER_FLAGS.techPreview which can throw if SERVER_FLAGS is undefined;
update the handler (function name: handler) to defensively read the flag using
optional chaining and a default false (e.g., base the value on
window.SERVER_FLAGS?.techPreview || false or
Boolean(window.SERVER_FLAGS?.techPreview)) before calling
setFeatureFlag(FLAG_TECH_PREVIEW, ...), ensuring no runtime TypeError when
SERVER_FLAGS is missing.

[vojtechszocs]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: logonoff, vojtechszocs

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• frontend/OWNERS [logonoff,vojtechszocs]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[logonoff]

in a dev instance, turned off -tech-preview bridge flag. refreshed console and observed that window.store.getState().FLAGS.toObject()['TECH_PREVIEW'] was false. turned it on and noticed that the flag is true

/verified by @logonoff

[openshift-ci-robot]

@logonoff: This PR has been marked as verified by @logonoff.

Details

In response to this:

in a dev instance, turned off -tech-preview bridge flag. refreshed console and observed that window.store.getState().FLAGS.toObject()['TECH_PREVIEW'] was false. turned it on and noticed that the flag is true

/verified by @logonoff

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD c99c674 and 2 for PR HEAD 762a071 in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 98409e8 and 1 for PR HEAD 762a071 in total

[logonoff]

/retest

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 1a68f54 and 0 for PR HEAD 762a071 in total

[openshift-ci-robot]

/hold

Revision 762a071 was retested 3 times: holding

[logonoff]

/unhold
/retest

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 1a68f54 and 2 for PR HEAD 762a071 in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD d101674 and 1 for PR HEAD 762a071 in total

[openshift-ci]

@logonoff: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.