@equinor/[email protected]

Minor Changes

• #3775 1827381 Thanks @odinr! - Add filtering options for telemetry messages passed from provider to adapters and parent providers.

  New Features

  • setAdapterFilter: Filter which telemetry items are passed to adapters
  • setRelayFilter: Filter which telemetry items are relayed to parent providers

  Usage

  enableTelemetry(configurator, {
    configure: (builder) => {
      // Only send exceptions to adapters
      builder.setAdapterFilter((item) => item.type === TelemetryType.Exception);
  
      // Only relay important events to parent provider
      builder.setRelayFilter(
        (item) =>
          item.type === TelemetryType.Exception ||
          item.scope?.includes("critical")
      );
    },
  });

  Hierarchical Filtering

  This feature enables filtering at each level of hierarchical telemetry setups (bootstrap → portal → apps), allowing:

  • Portal instances to filter which events reach bootstrap adapters
  • App instances to filter which events reach portal providers
  • Performance optimization by filtering unnecessary telemetry before processing
  • Privacy control by preventing sensitive telemetry from flowing up the hierarchy

  Backward Compatibility

  Existing code continues to work without filters - all items pass through by default when no filters are configured.

  Closes: #3774

@equinor/[email protected]

Patch Changes

• Updated dependencies []:
  • @equinor/[email protected]

@equinor/[email protected]

Patch Changes

• Updated dependencies []:
  • @equinor/[email protected]

@equinor/[email protected]

Patch Changes

• Updated dependencies []:
  • @equinor/[email protected]
  • @equinor/[email protected]

@equinor/[email protected]

Patch Changes

• Updated dependencies []:
  • @equinor/[email protected]
  • @equinor/[email protected]

@equinor/[email protected]

Minor Changes

• 393f163 Thanks @Noggling! - Portal Tags Now Support Any String Value

  Portal tagging functionality has been enhanced to accept any string value for tags instead of being restricted to predefined enum values.

  Breaking Changes

  • Removed AllowedPortalTags enum: The enum that previously restricted portal tags to only 'latest' and 'preview' has been removed.
  • No longer exported: AllowedPortalTags is no longer exported from @equinor/fusion-framework-cli/bin.

  Migration

  If you were importing and using AllowedPortalTags:

  // Before
  import { AllowedPortalTags } from '@equinor/fusion-framework-cli/bin';
  await tagPortal({ tag: AllowedPortalTags.Latest, ... });
  
  // After
  await tagPortal({ tag: 'latest', ... });

  New Flexibility

  You can now use any string value for portal tags:

  # Common tags still work
  ffc portal publish --tag latest
  ffc portal publish --tag preview
  
  # New flexibility with custom tags
  ffc portal publish --tag next
  ffc portal publish --tag stable
  ffc portal publish --tag v2.0.0-beta
  ffc portal publish --tag release-candidate
  ffc portal tag custom-environment --package [email protected]

  Enhanced Documentation

  • Updated CLI help text with practical examples
  • Added common tag examples (latest, preview, next, stable) in documentation
  • Maintained guidance while showing flexibility

  Validation

  • Tags must be non-empty strings
  • No other restrictions on tag format or content
  • Backward compatibility maintained for existing tag values

  This change provides much greater flexibility for deployment workflows while maintaining the same API structure and functionality.

@equinor/[email protected]

Patch Changes

• #3714 11fe961 Thanks @odinr! - Update FrameworkConfigurator.configureMsal to use MsalClientConfig instead of AuthClientConfig.

  This change aligns the framework configurator with the updated MSAL module types while maintaining backward compatibility through type aliases.

• Updated dependencies [11fe961, 11fe961, 11fe961, 11fe961]:

  • @equinor/[email protected]
  • @equinor/[email protected]
  • @equinor/[email protected]

@equinor/[email protected]

Patch Changes

• Updated dependencies [11fe961, 11fe961, 11fe961, 11fe961]:
  • @equinor/[email protected]
  • @equinor/[email protected]
  • @equinor/[email protected]

@equinor/[email protected]

Patch Changes

• #3714 11fe961 Thanks @odinr! - Fix MSAL v4 compatibility issues in SPA plugin.

  • Update MSAL client configuration to use nested auth object structure
  • Replace deprecated defaultAccount with account property
  • Update acquireToken calls to use MSAL v4 request structure

  These changes ensure the SPA plugin works correctly with MSAL v4 while maintaining backward compatibility.

• Updated dependencies [11fe961, 11fe961, 11fe961, 11fe961]:

  • @equinor/[email protected]
  • @equinor/[email protected]
  • @equinor/[email protected]

@equinor/[email protected]

Patch Changes

• #3714 11fe961 Thanks @odinr! - Fix MSAL v4 compatibility in React framework useCurrentUser hook.

  • Replace deprecated defaultAccount with account property
  • Ensure proper null/undefined handling for account information
  • Maintain type safety for AccountInfo return type

  This change ensures the React framework hook works correctly with MSAL v4 while maintaining backward compatibility.

• Updated dependencies [11fe961]:

  • @equinor/[email protected]
  • @equinor/[email protected]