Feat/env toggle #1192

bjorngoa · 2025-12-04T08:04:02Z

Azure DevOps links

User story

AB#667565

This pull request introduces a new Environment Toggle feature to the Account section, allowing users to select and display active environment-specific features. The implementation includes new UI components, updates to the Account avatar and button to reflect environment and impersonation status, and removes the old ImpersonateAvatar in favor of a more flexible status-based avatar system. Additionally, dependencies are updated and minor styling improvements are made.

Added a new EnvironmentToggle component, enabling users to select active environment features from a combobox, with selections persisted in local storage and reflected throughout the Account UI.

…eatures

Copilot

Pull request overview

This PR introduces an environment toggle feature that allows users to switch between production and current environment for specific features (SAM API calls). The implementation adds localStorage-based feature toggles with visual indicators in the TopBar account section.

Key Changes:

Added two custom hooks for managing environment toggle state and reading active toggles from localStorage
Integrated environment avatar and chips into the account UI to visually indicate when non-production features are active
Created a settings panel in the Account dropdown for toggling features with apply/cancel functionality

Reviewed changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated 16 comments.

Show a summary per file

File	Description
`src/organisms/TopBar/Account/environmentToggles/hooks/useToggleActiveEnvironment.ts`	New hook to read active environment features from localStorage on component mount
`src/organisms/TopBar/Account/environmentToggles/hooks/useEnvironmentToggle.ts`	New hook to manage feature toggle state with save/reset functionality and page reload on apply
`src/organisms/TopBar/Account/EnvironmentAvatar.tsx`	New component displaying a warning-styled avatar when environment features are active
`src/organisms/TopBar/Account/AccountButton.tsx`	Updated to show environment feature chips and prioritize environment avatar over impersonation avatar
`src/organisms/TopBar/Account/AccountAvatar.tsx`	Updated to display environment avatar with label when features are active
`src/organisms/TopBar/Account/Account.tsx`	Added environment toggle switches section with apply/cancel buttons, only shown in non-production
`src/organisms/TopBar/Account/Account.styles.ts`	Added `SwitchWrapper` styling and updated `ButtonWrapper` to support multiple buttons in a row
`src/atoms/enums/Environment.ts`	Added `PointToProdFeaturesLocalStorageKey` enum defining four toggleable features

Comments suppressed due to low confidence (1)

src/organisms/TopBar/Account/AccountButton.tsx:67

The avatar display priority might not align with expectations. Currently, environment features take precedence over impersonation (isActiveFeatureOnCurrentEnvironment is checked first). This means when both an environment toggle is active AND a user is being impersonated, only the environment avatar shows. Consider if this is the intended behavior, or if impersonation should take priority since it's a more critical security indicator.

          {isActiveFeatureOnCurrentEnvironment ? (
            <EnvironmentAvatar size={36} />
          ) : activeImpersonationUser ? (
            <ImpersonateAvatar size={36} />
          ) : (
            <ProfileAvatar size={36} name={account?.name} url={photo} />
          )}

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

src/organisms/TopBar/Account/Account.tsx

src/organisms/TopBar/Account/environmentToggles/hooks/useEnvironmentToggle.ts

Copilot · 2025-12-04T08:09:16Z

src/organisms/TopBar/Account/environmentToggles/hooks/useToggleActiveEnvironment.ts

+      activeFeaturesOnCurrentEnvironment != null
+        ? activeFeaturesOnCurrentEnvironment.length > 0
+        : false,


The null check != null is redundant since the state is initialized to [] (not null) and never set to null anywhere in the code. This condition will always be true. Consider simplifying to just check the length: activeFeaturesOnCurrentEnvironment.length > 0.

Suggested change

activeFeaturesOnCurrentEnvironment != null

? activeFeaturesOnCurrentEnvironment.length > 0

: false,

activeFeaturesOnCurrentEnvironment.length > 0,

src/organisms/TopBar/Account/Account.tsx

src/organisms/TopBar/Account/environmentToggles/hooks/useEnvironmentToggle.ts

src/organisms/TopBar/Account/Account.tsx

src/organisms/TopBar/Account/environmentToggles/hooks/useToggleActiveEnvironment.ts

src/organisms/TopBar/Account/Account.tsx

src/atoms/enums/Environment.ts

github-actions · 2025-12-04T08:11:27Z

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	99.17% (🎯 100%)	16442 / 16578
🔵	Statements	99.17% (🎯 100%)	16442 / 16578
🔵	Functions	99.07% (🎯 100%)	1178 / 1189
🔵	Branches	99.31% (🎯 100%)	4031 / 4059

File Coverage

File	Stmts	Branches	Functions	Lines
Changed Files
src/atoms/utils/environmentToggle.ts	89.18%	66.66%	66.66%	89.18%
src/organisms/TopBar/Account/Account.styles.ts	100%	100%	100%	100%
src/organisms/TopBar/Account/Account.tsx	94.93%	90.9%	100%	94.93%
src/organisms/TopBar/Account/AccountAvatar.tsx	66.66%	66.66%	60%	66.66%
src/organisms/TopBar/Account/AccountButton.tsx	78.57%	58.82%	50%	78.57%
src/organisms/TopBar/Account/EnvironmentToggle.tsx	18.18%	100%	50%	18.18%
src/organisms/TopBar/Account/StatusAvatar.tsx	100%	100%	60%	100%
src/organisms/TopBar/Account/StatusChips.tsx	100%	100%	100%	100%
src/organisms/TopBar/Account/ImpersonateMenu/DeleteUser/DeleteUser.tsx	100%	100%	100%	100%

Generated in workflow #2003 for commit 70b87c9 by the Vitest Coverage Report Action

Copilot

Pull request overview

Copilot reviewed 8 out of 8 changed files in this pull request and generated 7 comments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

src/organisms/TopBar/Account/AccountButton.tsx

src/organisms/TopBar/Account/Account.tsx

src/organisms/TopBar/Account/environmentToggles/hooks/useToggleActiveEnvironment.ts

src/organisms/TopBar/Account/AccountAvatar.tsx

…EnvironmentToggleType interface

Copilot

Pull request overview

Copilot reviewed 8 out of 8 changed files in this pull request and generated 5 comments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

src/organisms/TopBar/Account/EnvironmentAvatar.tsx

src/organisms/TopBar/Account/Account.tsx

src/organisms/TopBar/Account/environmentToggles/hooks/useToggleActiveEnvironment.ts

src/organisms/TopBar/Account/AccountButton.tsx

Copilot · 2025-12-09T07:05:34Z

src/organisms/TopBar/Account/AccountButton.tsx

+            {activeFeatures[0].split('-key')[0]}
+          </ImpersonationRoleChip>
+        )}
+        {activeFeatures && activeFeatures.length > 1 && (


Redundant null check: The check activeFeatures && is unnecessary since activeFeatures is never null (it's initialized to an empty array).

Simplify to: {activeFeatures.length > 1 && (

Suggested change

{activeFeatures && activeFeatures.length > 1 && (

{activeFeatures.length > 1 && (

aslakihle · 2025-12-11T13:55:40Z

src/organisms/TopBar/Account/Account.tsx

+        <EnvironmentToggleWrapper>
+          {enableEnvironmentToggle &&
+            ACTIVE_ENVIRONMENT !== EnvironmentType.PRODUCTION && (
+              <EnvironmentToggle
+                setEnvironmentToggle={setEnvironmentToggle}
+                environmentToggle={environmentToggle}
+              />
+            )}
+        </EnvironmentToggleWrapper>


Should this wrapper be inside the EnvironmentToggle component?
How does it look now if you dont have environment toggle enabled?

aslakihle · 2025-12-11T13:59:38Z

src/atoms/utils/environmentToggle.ts

@@ -0,0 +1,3 @@
+export function getActiveFeatureDisplayName(activeFeature: string) {


This could take the enum that exists in SAM as a type.
And the util itself could do a replace of "-" to a space " " and maybe capitalize the first letter, and they should look better as names.
And not do the split on "-key", gven that the comments on the SAM PR about changing the names (to "feature-toggle" for example) is done

…tures and improve display name handling

Copilot

Pull request overview

Copilot reviewed 11 out of 11 changed files in this pull request and generated 5 comments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2025-12-12T11:03:46Z

src/organisms/TopBar/Account/StatusAvatar.tsx

+const Wrapper = styled.div<StatusVariantProps>`
+  width: fit-content;
+  border: 2px solid
+    ${({ $variant }) => {
+      switch ($variant) {
+        case 'combined':
+          return colors.interactive.success__resting.rgba;
+        case 'environment':
+          return colors.interactive.success__resting.rgba;
+        case 'impersonate':
+          return colors.interactive.warning__resting.rgba;
+        default:
+          return colors.interactive.warning__resting.rgba;
+      }
+    }};
+  border-radius: 50%;
+  > div:first-child {
+    background: ${({ $variant }) => {
+      switch ($variant) {
+        case 'combined':
+          return colors.interactive.warning__text.rgba;
+        case 'environment':
+          return colors.interactive.success__text.rgba;
+        case 'impersonate':
+          return colors.interactive.warning__text.rgba;
+        default:
+          return colors.interactive.warning__text.rgba;
+      }
+    }};


There is significant code duplication in the switch statement logic for variant-based styling. The same switch statement pattern appears in StatusAvatar.tsx (lines 17-26 and 30-40), AccountButton.tsx (lines 27-38), and AccountAvatar.tsx (lines 28-51). Consider extracting this logic into a shared utility function or constants object to improve maintainability.

Suggested change

const Wrapper = styled.div<StatusVariantProps>`

width: fit-content;

border: 2px solid

${({ $variant }) => {

switch ($variant) {

case 'combined':

return colors.interactive.success__resting.rgba;

case 'environment':

return colors.interactive.success__resting.rgba;

case 'impersonate':

return colors.interactive.warning__resting.rgba;

default:

return colors.interactive.warning__resting.rgba;

}

}};

border-radius: 50%;

> div:first-child {

background: ${({ $variant }) => {

switch ($variant) {

case 'combined':

return colors.interactive.warning__text.rgba;

case 'environment':

return colors.interactive.success__text.rgba;

case 'impersonate':

return colors.interactive.warning__text.rgba;

default:

return colors.interactive.warning__text.rgba;

}

}};

// Utility functions to map variant to color

function getBorderColorForVariant(variant?: StatusVariant) {

switch (variant) {

case 'combined':

case 'environment':

return colors.interactive.success__resting.rgba;

case 'impersonate':

return colors.interactive.warning__resting.rgba;

default:

return colors.interactive.warning__resting.rgba;

}

}

function getBackgroundColorForVariant(variant?: StatusVariant) {

switch (variant) {

case 'combined':

case 'impersonate':

return colors.interactive.warning__text.rgba;

case 'environment':

return colors.interactive.success__text.rgba;

default:

return colors.interactive.warning__text.rgba;

}

}

const Wrapper = styled.div<StatusVariantProps>`

width: fit-content;

border: 2px solid

${({ $variant }) => getBorderColorForVariant($variant)};

border-radius: 50%;

> div:first-child {

background: ${({ $variant }) => getBackgroundColorForVariant($variant)};

Copilot · 2025-12-12T11:03:47Z

src/atoms/utils/environmentToggle.ts

+export function getActiveFeatureDisplayName(
+  activeFeature: EnvironmentToggleFeatures
+) {
+  return (
+    activeFeature.charAt(0).toUpperCase() +
+    activeFeature.slice(1).replaceAll('-', ' ')


The function name "getActiveFeatureDisplayName" is misleading. The parameter is named "activeFeature", but the function simply formats any string by capitalizing the first letter and replacing hyphens with spaces. It doesn't specifically get or determine which feature is active. Consider renaming to something like "formatFeatureName" or "toDisplayName" to better reflect what it does.

Suggested change

export function getActiveFeatureDisplayName(

activeFeature: EnvironmentToggleFeatures

) {

return (

activeFeature.charAt(0).toUpperCase() +

activeFeature.slice(1).replaceAll('-', ' ')

export function formatFeatureName(

feature: EnvironmentToggleFeatures

) {

return (

feature.charAt(0).toUpperCase() +

feature.slice(1).replaceAll('-', ' ')

Copilot · 2025-12-12T11:03:47Z

src/organisms/TopBar/Account/AccountButton.tsx

+            getActiveFeatureDisplayName(item.value as EnvironmentToggleFeatures)
+          );
+
    const impersonationRoles = activeImpersonationUser?.roles?.sort() ?? [];


The sort() method mutates the original array. This could cause unintended side effects if the roles array is used elsewhere. Consider using toSorted() or creating a copy with slice() before sorting to avoid mutation.

Suggested change

const impersonationRoles = activeImpersonationUser?.roles?.sort() ?? [];

const impersonationRoles = activeImpersonationUser?.roles?.toSorted() ?? [];

Copilot · 2025-12-12T11:03:47Z

src/organisms/TopBar/Account/AccountButton.tsx

+        return (
+          <StatusAvatar
+            size={36}
+            name={environmentToggle.map((x) => x.value).join(', ')}


TypeScript may not properly narrow the type of environmentToggle in this block. While isActiveFeatureOnCurrentEnvironment checks that environmentToggle is not null/undefined, TypeScript might still treat it as potentially undefined when calling map() on line 71. Consider using a non-null assertion (environmentToggle!.map) or restructuring the condition to help TypeScript narrow the type.

Suggested change

name={environmentToggle.map((x) => x.value).join(', ')}

name={environmentToggle!.map((x) => x.value).join(', ')}

Copilot · 2025-12-12T11:03:47Z

src/organisms/TopBar/Account/AccountButton.tsx

+export const StatusChip = styled(Chip)<StatusVariantProps>`
+  background: ${({ $variant }) => {
+    switch ($variant) {
+      case 'combined':
+        return colors.interactive.warning__resting.rgba;
+      case 'environment':
+        return colors.interactive.success__resting.rgba;
+      case 'impersonate':
+        return colors.interactive.warning__resting.rgba;
+      default:
+        return colors.interactive.warning__resting.rgba;
+    }
+  }};


There is significant code duplication in the switch statement logic for variant-based styling. The same switch statement pattern appears in StatusAvatar.tsx (lines 17-26 and 30-40), AccountButton.tsx (lines 27-38), and AccountAvatar.tsx (lines 28-51). Consider extracting this logic into a shared utility function or constants object to improve maintainability.

Suggested change

export const StatusChip = styled(Chip)<StatusVariantProps>`

background: ${({ $variant }) => {

switch ($variant) {

case 'combined':

return colors.interactive.warning__resting.rgba;

case 'environment':

return colors.interactive.success__resting.rgba;

case 'impersonate':

return colors.interactive.warning__resting.rgba;

default:

return colors.interactive.warning__resting.rgba;

}

}};

// Extracted variant-to-color mapping

const STATUS_VARIANT_COLORS: Record<string, string> = {

combined: colors.interactive.warning__resting.rgba,

environment: colors.interactive.success__resting.rgba,

impersonate: colors.interactive.warning__resting.rgba,

};

export const StatusChip = styled(Chip)<StatusVariantProps>`

background: ${({ $variant }) =>

STATUS_VARIANT_COLORS[$variant ?? 'combined'] ||

colors.interactive.warning__resting.rgba};

…improve loading state handling

aslakihle

😎

Copilot

Pull request overview

Copilot reviewed 13 out of 14 changed files in this pull request and generated 6 comments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2025-12-12T12:50:16Z

src/organisms/TopBar/Account/StatusAvatar.tsx

+    ${({ $variant }) => {
+      switch ($variant) {
+        case 'combined':
+          return colors.interactive.success__resting.rgba;
+        case 'environment':
+          return colors.interactive.success__resting.rgba;
+        case 'impersonate':
+          return colors.interactive.warning__resting.rgba;
+        default:
+          return colors.interactive.warning__resting.rgba;
+      }


The switch statement has identical return values for 'combined', 'impersonate', and 'default' cases. This duplication can be simplified by combining these cases together to improve maintainability.

Copilot · 2025-12-12T12:50:16Z

src/organisms/TopBar/Account/StatusAvatar.tsx

+    background: ${({ $variant }) => {
+      switch ($variant) {
+        case 'combined':
+          return colors.interactive.warning__text.rgba;
+        case 'environment':
+          return colors.interactive.success__text.rgba;
+        case 'impersonate':
+          return colors.interactive.warning__text.rgba;
+        default:
+          return colors.interactive.warning__text.rgba;
+      }
+    }};


The switch statement has identical return values for 'combined', 'impersonate', and 'default' cases. This duplication can be simplified by combining these cases together to improve maintainability.

Copilot · 2025-12-12T12:50:17Z

src/organisms/TopBar/Account/EnvironmentToggle.tsx

+    setTimeout(() => {
+      queryClient.invalidateQueries();
+      setIsLoading(false);
+    }, 2000);


The hardcoded 2000ms timeout value should be extracted as a named constant with a descriptive name (e.g., QUERY_INVALIDATION_DELAY) to improve code maintainability and make the intent clearer.

Copilot · 2025-12-12T12:50:17Z

src/organisms/TopBar/Account/EnvironmentToggle.tsx

+    setEnvironmentToggle(value);
+    setIsLoading(true);
+    setTimeout(() => {
+      queryClient.invalidateQueries();


Calling invalidateQueries without any filter will invalidate all queries in the application, which may cause unnecessary network requests and performance issues. Consider targeting specific query keys that are affected by the environment toggle change.

Suggested change

queryClient.invalidateQueries();

queryClient.invalidateQueries(['environment']);

Copilot · 2025-12-12T12:50:17Z

src/organisms/TopBar/Account/AccountButton.tsx

+  background: ${({ $variant }) => {
+    switch ($variant) {
+      case 'combined':
+        return colors.interactive.warning__resting.rgba;
+      case 'environment':
+        return colors.interactive.success__resting.rgba;
+      case 'impersonate':
+        return colors.interactive.warning__resting.rgba;
+      default:
+        return colors.interactive.warning__resting.rgba;
+    }
+  }};


The switch statement has identical return values for 'combined', 'impersonate', and 'default' cases. This duplication can be simplified by combining these cases together to improve maintainability.

Copilot · 2025-12-12T12:50:18Z

src/organisms/TopBar/Account/AccountAvatar.tsx

+  background: ${({ $variant }) => {
+    switch ($variant) {
+      case 'combined':
+        return colors.interactive.warning__resting.rgba;
+      case 'environment':
+        return colors.interactive.success__resting.rgba;
+      case 'impersonate':
+        return colors.interactive.warning__resting.rgba;
+      default:
+        return colors.interactive.warning__resting.rgba;
+    }
+  }};
+  outline-color: ${({ $variant }) => {
+    switch ($variant) {
+      case 'combined':
+        return colors.interactive.success__resting.rgba;
+      case 'environment':
+        return colors.interactive.success__resting.rgba;
+      case 'impersonate':
+        return colors.interactive.warning__resting.rgba;
+      default:
+        return colors.interactive.warning__resting.rgba;
+    }
+  }};


The switch statement has identical return values for 'combined', 'impersonate', and 'default' cases. This duplication can be simplified by combining these cases together to improve maintainability.

…ariantColors for dynamic styling

…rs for dynamic styling

Copilot

Pull request overview

Copilot reviewed 14 out of 15 changed files in this pull request and generated 2 comments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

src/organisms/TopBar/Account/AccountAvatar.tsx

src/organisms/TopBar/Account/StatusAvatar.tsx

…or dynamic styling

aslakihle

😎

bjorngoa added 6 commits December 4, 2025 09:01

✨ Add SwitchWrapper style for improved layout in Account component

aa9d2d6

✨ Add custom hook for toggling active environment features

8053fc2

✨ Implement custom hook for managing environment feature toggles

fa68c1a

✨ Add EnvironmentAvatar component for displaying active environment f…

2c8c3c2

…eatures

✨ Add PointToProdFeaturesLocalStorageKey enum for feature toggle keys

9a857f6

✨ Add environment feature toggle functionality to Account component

acf9a0f

Copilot AI review requested due to automatic review settings December 4, 2025 08:04

bjorngoa had a problem deploying to feature December 4, 2025 08:04 — with GitHub Actions Error

Copilot started reviewing on behalf of bjorngoa December 4, 2025 08:04 View session

Copilot finished reviewing on behalf of bjorngoa December 4, 2025 08:07

Copilot AI reviewed Dec 4, 2025

View reviewed changes

bjorngoa added 2 commits December 4, 2025 09:55

♻️ Refactor feature toggle handler in Account component

eaa8d9c

♻️ Remove unused feature toggle handler in Account component

1310fce

bjorngoa had a problem deploying to feature December 4, 2025 08:56 — with GitHub Actions Error

♻️ remove redundant fragment

91fa6b5

Copilot AI review requested due to automatic review settings December 4, 2025 08:59

bjorngoa had a problem deploying to feature December 4, 2025 08:59 — with GitHub Actions Error

Copilot started reviewing on behalf of bjorngoa December 4, 2025 09:00 View session

Copilot finished reviewing on behalf of bjorngoa December 4, 2025 09:02

Copilot AI reviewed Dec 4, 2025

View reviewed changes

♻️ Remove empty Typography component in Account component

0ea0fba

bjorngoa had a problem deploying to feature December 4, 2025 10:11 — with GitHub Actions Error

♻️ Refactor environment toggle implementation in Account component

c82e3f6

Copilot AI review requested due to automatic review settings December 9, 2025 07:00

bjorngoa had a problem deploying to feature December 9, 2025 07:00 — with GitHub Actions Error

Copilot started reviewing on behalf of bjorngoa December 9, 2025 07:00 View session

bjorngoa added 2 commits December 9, 2025 08:05

✨ Add EnvironmentToggle component for managing environment selections

dc7a49f

♻️ Update import path for PointToProdFeaturesLocalStorageKey and add …

00277d3

…EnvironmentToggleType interface

Copilot AI reviewed Dec 9, 2025

View reviewed changes

bjorngoa had a problem deploying to feature December 11, 2025 13:42 — with GitHub Actions Error

aslakihle requested changes Dec 11, 2025

View reviewed changes

♻️ Refactor environment toggle components to use EnvironmentToggleFea…

39c6fbb

…tures and improve display name handling

Copilot AI review requested due to automatic review settings December 12, 2025 11:00

bjorngoa had a problem deploying to feature December 12, 2025 11:00 — with GitHub Actions Error

Copilot started reviewing on behalf of bjorngoa December 12, 2025 11:00 View session

Copilot AI reviewed Dec 12, 2025

View reviewed changes

♻️ Update environment toggle components to use formatFeatureName and …

0a40eb9

…improve loading state handling

bjorngoa had a problem deploying to feature December 12, 2025 12:01 — with GitHub Actions Error

🔖 10.8.0

6441f55

Copilot AI review requested due to automatic review settings December 12, 2025 12:46

bjorngoa had a problem deploying to feature December 12, 2025 12:46 — with GitHub Actions Error

Copilot started reviewing on behalf of bjorngoa December 12, 2025 12:46 View session

aslakihle previously approved these changes Dec 12, 2025

View reviewed changes

Copilot AI reviewed Dec 12, 2025

View reviewed changes

♻️ Introduce StatusVariant type and refactor StatusAvatar to use getV…

bb24fb0

…ariantColors for dynamic styling

bjorngoa dismissed aslakihle’s stale review via bb24fb0 December 12, 2025 13:25

bjorngoa had a problem deploying to feature December 12, 2025 13:25 — with GitHub Actions Error

bjorngoa added 2 commits December 12, 2025 14:41

♻️ Refactor AccountAvatar and AccountButton to utilize getVariantColo…

90fb463

…rs for dynamic styling

♻️ Remove unused getVariantColors import from AccountAvatar

19083b1

Copilot AI review requested due to automatic review settings December 12, 2025 13:42

bjorngoa had a problem deploying to feature December 12, 2025 13:42 — with GitHub Actions Error

Copilot started reviewing on behalf of bjorngoa December 12, 2025 13:42 View session

Copilot AI reviewed Dec 12, 2025

View reviewed changes

src/organisms/TopBar/Account/AccountAvatar.tsx Outdated Show resolved Hide resolved

src/organisms/TopBar/Account/StatusAvatar.tsx Show resolved Hide resolved

♻️ Refactor AccountAvatar and AccountButton to use getVariantColors f…

70b87c9

…or dynamic styling

bjorngoa had a problem deploying to feature December 12, 2025 13:51 — with GitHub Actions Error

aslakihle approved these changes Dec 12, 2025

View reviewed changes

aslakihle merged commit f5e7b8f into main Dec 15, 2025
9 of 11 checks passed

aslakihle deleted the feat/env-toggle branch December 15, 2025 10:16

	{activeFeatures && activeFeatures.length > 1 && (
	{activeFeatures.length > 1 && (

		@@ -0,0 +1,3 @@
		export function getActiveFeatureDisplayName(activeFeature: string) {

	const impersonationRoles = activeImpersonationUser?.roles?.sort() ?? [];
	const impersonationRoles = activeImpersonationUser?.roles?.toSorted() ?? [];

	name={environmentToggle.map((x) => x.value).join(', ')}
	name={environmentToggle!.map((x) => x.value).join(', ')}

	queryClient.invalidateQueries();
	queryClient.invalidateQueries(['environment']);

Feat/env toggle #1192

Feat/env toggle #1192

Uh oh!

Conversation

bjorngoa commented Dec 4, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Azure DevOps links

User story

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Uh oh!

Copilot AI Dec 4, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

github-actions bot commented Dec 4, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Coverage Report

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Copilot AI Dec 9, 2025

Choose a reason for hiding this comment

Uh oh!

aslakihle Dec 11, 2025

Choose a reason for hiding this comment

Uh oh!

aslakihle Dec 11, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Dec 12, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 12, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 12, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 12, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 12, 2025

Choose a reason for hiding this comment

Uh oh!

aslakihle left a comment

Choose a reason for hiding this comment

bjorngoa commented Dec 4, 2025 •

edited

Loading

github-actions bot commented Dec 4, 2025 •

edited

Loading

aslakihle Dec 11, 2025 •

edited

Loading