You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Each row in the import flow shows: a preview of the incoming style (node or edge), the type name, a checkbox for selection, a conflict badge (when a matching shared style exists), and a toggle to clear user customization (off by default). How should these elements be laid out within a single row? How does the row adapt for narrow vs wide containers (relevant to the modal vs full-screen decision)?
Expected Outcome
A prototype of the row component at a few different widths, with realistic content (mix of node and edge types, some conflicting, some not). Recommendation on layout.
Question
Each row in the import flow shows: a preview of the incoming style (node or edge), the type name, a checkbox for selection, a conflict badge (when a matching shared style exists), and a toggle to clear user customization (off by default). How should these elements be laid out within a single row? How does the row adapt for narrow vs wide containers (relevant to the modal vs full-screen decision)?
Expected Outcome
A prototype of the row component at a few different widths, with realistic content (mix of node and edge types, some conflicting, some not). Recommendation on layout.
Related Issues
Important
Internal only — this issue is maintained by the core team and is not accepting external contributions.