trTryGhost
GitHubGhostWorkspace
GitHub
  • CI Pipeline Executions
    • Current executionSucceededfeat/member-details-react-labs-flag
    • Configuration
    • Self-Healing CI
    • Project Graph
    • Resource Usage
    • Analysis
    • Conformance
  • Runs
    • Current runSucceeded
    • Tasks
    • Resource Usage
Insights
  • Compare tasks
  • Analytics
    Changed the member detail route to serve React behind a Labs flag no ref This wires up the flag added earlier in the stack: `/members/:member_id` now resolves to MemberDetailGate, which reads the Labs flag at render time and serves either the React screen or the Ember fallback, so toggling it in Developer Experiments swaps implementations without a rebuild. Ember owns the URL in every uncertain case (config failed, empty, flag absent) — only an explicit true renders React — but config still loading holds for a paint rather than falling back, which would flash the Ember screen on cold loads. The Ember route aborts the transition when the flag is on so only one tree is ever mounted and its test attributes can't collide with React's. The e2e suite now generates one describe block per flag state and runs the same assertions against both, with the page object matching either implementation's markup rather than branching, so a behaviour gap fails instead of hiding.
    nx run @tryghost/admin-x-settings:test:acceptance
Succeeded
Linux
4 CPU cores
c76aa73129345
91%

Cache hits

10 of 11 tasks used cache.

Protect cache integrity with sandboxing

Get faster results

Learn how to enable distribution.

Atomizer enabled

11 groups of tasks optimized.

© 2026 - Nx Cloud

Terms of ServicePrivacy PolicyChangelogStatusDocsContact Nx CloudPricingCompany@NxDevTools