tr
TryGhost
GitHub
Ghost
Workspace
GitHub
CI Pipeline Executions
Current execution
Succeeded
ber-3949-portal-custom-fields
Runs and Agents
Timeline
Beta
Configuration
Self-Healing CI
Project Graph
Circular Dependencies
Enterprise
Resource Usage
Analysis
Conformance
Enterprise
Runs
Current run
Succeeded
Tasks
Resource Usage
Insights
Compare tasks
Analytics
Sign in
Toggle sidebar
Added browser coverage for a member editing their custom fields ref https://linear.app/ghost/issue/BER-3949/members-see-and-edit-their-opened-custom-fields-in-portal-account These behaviours live at seams a unit test cannot reach: state that outlives the page it was set from, and how a row lays out once a message appears under it. A component test that supplies its own context or asserts on a class name passes straight through either. Driven in a browser instead, a refused part is marked and its neighbour is not, leaving the page and returning shows the refusal gone along with the text it belonged to, and a refused part leaves the box beside it level.
nx run ghost-monorepo:lint:boundaries
⌘K
Succeeded
nx run ghost-monorepo:lint:boundaries
Click to copy
Linux
4 CPU cores
read-write
access token used
756701dd
30669
GitHub
Ghost
Workspace