Overview - Ghost

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
29345
b9a5b48e 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.
by Rob Lester
Succeeded
29345
75064172 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.
by Rob Lester
Succeeded
29345
0874d5a8 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.
by Rob Lester
Failed
29345
6608ec6e 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.
by Rob Lester
Succeeded
29345
c9ff31de 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.
by Rob Lester
Succeeded
29345
9e7a146f 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.
by Rob Lester
Succeeded
29345
7e946ae2 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.
by Rob Lester
Failed
29345
6fa61fa2 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.
by Rob Lester