Skip to content

Relocate immersive editor components to a common namespace#6624

Merged
cstns merged 6 commits intomainfrom
chore/extract-immersive-editor-components-into-a-global-namespace
Feb 5, 2026
Merged

Relocate immersive editor components to a common namespace#6624
cstns merged 6 commits intomainfrom
chore/extract-immersive-editor-components-into-a-global-namespace

Conversation

@cstns
Copy link
Contributor

@cstns cstns commented Feb 3, 2026

Prerequisites

branched of #6623 which needs to be merged in first

Description

Relocating immersive editor components in a common namespace for them to be used by the remote instance editor as well

Related Issue(s)

part of #6599
closes #6639

Checklist

  • I have read the contribution guidelines
  • Suitable unit/system level tests have been added and they pass
  • Documentation has been updated
    • Upgrade instructions
    • Configuration details
    • Concepts
  • Changes flowforge.yml?
    • Issue/PR raised on FlowFuse/helm to update ConfigMap Template
    • Issue/PR raised on FlowFuse/CloudProject to update values for Staging/Production
  • Link to Changelog Entry PR, or note why one is not needed.

Labels

  • Includes a DB migration? -> add the area:migration label

@cstns cstns self-assigned this Feb 3, 2026
@codecov
Copy link

codecov bot commented Feb 3, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 76.66%. Comparing base (5b664d8) to head (baaa44e).
⚠️ Report is 11 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #6624   +/-   ##
=======================================
  Coverage   76.66%   76.66%           
=======================================
  Files         398      398           
  Lines       20103    20103           
  Branches     4841     4841           
=======================================
  Hits        15411    15411           
  Misses       4692     4692           
Flag Coverage Δ
backend 76.66% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@cstns cstns requested review from Steve-Mcl and dimitrieh and removed request for Steve-Mcl February 4, 2026 09:29
cstns added 3 commits February 4, 2026 11:32
…ferences to reflect the new naming convention. Simplify import paths for loading animations.
…xtract-immersive-editor-components-into-a-global-namespace
…omponents-into-a-global-namespace' into chore/extract-immersive-editor-components-into-a-global-namespace
Copy link
Contributor

@Steve-Mcl Steve-Mcl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good - works too :D

…xtract-immersive-editor-components-into-a-global-namespace
Base automatically changed from chore/extract-device-editor-nested-routes to main February 5, 2026 12:28
@cstns cstns merged commit 7ed08a3 into main Feb 5, 2026
26 of 27 checks passed
@cstns cstns deleted the chore/extract-immersive-editor-components-into-a-global-namespace branch February 5, 2026 15:06
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.

Relocate immersive editor components to a common namespace

2 participants