Skip to content

Design V2 bug bash: help us find and fix bugs in the new playground design #1096

Open

Description

@mttrbrts

The redesigned playground (Design V2) is now live behind a feature flag at https://playground.accordproject.org. It replaces the single-screen editor with a guided, step-based flow: Template → Text → Data → Logic → Simulate → Deploy.

It is still work in progress, and we would love the community's help to shake out bugs before it becomes the default. This issue is the hub for that effort.

How to enable Design V2

On the live site

  1. Open https://playground.accordproject.org
  2. Click the Settings (gear) icon in the sidebar
  3. In the General tab, switch on Enable Design v2 (Work in Progress)
  4. The page switches to the new layout. To switch back, use the gear icon at the bottom of the new left rail and turn the toggle off.

The setting is stored in your browser (localStorage key isDesignV2Enabled), so you can also run localStorage.setItem('isDesignV2Enabled', 'true') in the browser console and reload.

Locally

git clone https://github.com/<you>/template-playground.git
cd template-playground
npm install
npm run dev

Then enable the flag as above. The V2 code lives in src/components/designV2/, its state in src/store/designV2Store.ts, and unit tests in src/tests/components/designV2/. See DEVELOPERS.md for more.

What to test

Walk through every step with each sample template, then try to break it:

  • Introduce errors in text.md, model.cto, data.json and logic.ts and check the error messages, status chips and checklists
  • Switch templates mid-flow, use Back/Next and the stepper, reload, and open share links
  • Import templates (library and file; URL import is being removed in Design V2: remove "Import from URL" (blocked by CORS for most hosts) #1118) and every Deploy action (PDF, Markdown, share link, clipboard)
  • Narrow / mobile viewports, keyboard-only navigation, screen readers, and different browsers

Reporting a bug

  1. Search open issues first to avoid duplicates
  2. Open a new issue with Design V2 in the title, steps to reproduce, expected vs actual behaviour, browser/OS and a screenshot
  3. Mention this issue (Part of #1096) so it is linked here

Fixing a bug

Comment on the bug issue to say you are working on it, then open a PR that references it (Fixes #<issue>) and includes a test where practical. Please keep each PR to one bug.

Starter bugs

These were found in a quick pass over the live site and are good places to start. Status as of 16 Nov:

Thank you for helping make the new playground solid!

Activity

  1. sayanCodesDev commented on Nov 13, 2026

    @sayanCodesDev
    Contributor

    Hi @mttrbrts,

    Following up on the Starter bugs checklist in this tracking issue. Pull requests have been submitted for all four items and are ready for maintainer review:

    Starter Bug Summary Fix PR Author
    #1097 Data step false failure on text.md errors #1105 @sayanCodesDev
    #1098 Minified text error names & missing Monaco markers #1102 @sayanCodesDev
    #1099 Stale preview indicator and disabling exports on error #1106 @sayanCodesDev
    #1100 Logic step overlap & clipping on mobile screens #1104 @averif

    Each PR includes relevant test coverage or visual verification. Once reviewed and merged, all starter bugs from the list can be checked off!

  2. mttrbrts commented on Nov 16, 2026

    @mttrbrts
    SponsorMemberAuthor

    Bug bash progress update (16 Nov)

    Thanks to everyone who has reported bugs, opened fixes and reviewed each other's PRs. All open Design V2 PRs have now been reviewed. Here is where things stand.

    Starter bugs

    Bug Fix PR Status
    #1097: Data step fails for text.md errors #1105 ✅ Merged
    #1098: minified error name, no editor marker #1102 Changes requested. It currently strips the file name that #1105 relies on, and it removes line/column from model errors too.
    #1099: stale preview shown as "live" #1106 Changes requested, but only to revert the CSS reformatting. The fix itself is good.
    #1100: Logic step clipped on mobile #1104 Changes requested. Please narrow it to the #1100 fix and split the new mobile step picker into its own PR.

    Merged today

    Approved, waiting on CI

    Changes requested

    #1102, #1104, #1106, #1084, #1044, #1073. Each PR has a review with the details. Push an update and we'll take another look.

    Also in progress

    CI notes for contributors

    What's next

    The plan is to make Design V2 the default view, with the classic layout still available from Settings and a one-time banner to switch back (#1116). The bugs above should land first, so fixes to the open starter bugs are the most valuable thing right now.

    Please keep reporting what you find: put [Design V2] in the title, include steps to reproduce, and add Part of #1096.

  3. mttrbrts commented on Nov 16, 2026

    @mttrbrts
    SponsorMemberAuthor

    Quick follow-up: #1064 (stops a double-click starting two AI runs) and #1078 (Format disabled on an empty data editor, closes #1077) have now passed CI and are merged.

    That makes six Design V2 fixes merged today: #1105, #1067, #1092, #1083, #1064 and #1078. Thanks to everyone involved!

  4. mttrbrts commented on Nov 16, 2026

    @mttrbrts
    SponsorMemberAuthor

    New issues open for contributors, all labelled help wanted:

    #1119 and #1120 overlap (both decide which view V2 opens on), so please comment on the issue before starting, to avoid duplicate PRs. Each issue includes the cause, the files involved and acceptance criteria.

  5. mttrbrts commented on Nov 16, 2026

    @mttrbrts
    SponsorMemberAuthor

    One more for contributors, labelled help wanted:

    This overlaps with #1043 (Simulate pre-fills the Counter sample's CounterRequest), so one PR could fix both. Please comment on #1121 before starting.

  6. mttrbrts commented on Nov 16, 2026

    @mttrbrts
    SponsorMemberAuthor

    New feature issue for Design V2:

    This replaces the clipboard-based "Copy for AI" idea from the RFC #1108. A contributor has already offered to take it on in #1108, so please check #1122 before starting anything similar.

  7. mttrbrts commented on Nov 16, 2026

    @mttrbrts
    SponsorMemberAuthor

    New PR for Design V2:

    Please try it on the PR's Netlify deploy preview, especially as a first-time visitor (clear site data first) and when switching between classic and V2 with edits open, and report anything odd here.

    Known gap, not covered by #1123: the V2 Simulate step doesn't yet show the AI execution-mode controls that the classic layout has.

  8. Jenil1905 commented on Nov 18, 2026

    @Jenil1905
    Contributor

    I investigated the concurrency concern raised during the review of #1064 and reproduced it on clean upstream main at commit 4f760d0, using both sandbox and forced LLM execution with controlled pending responses.

    After initializing the contract and completing one trigger, I held a subsequent trigger pending and called initContract() again. The second initialization cleared the chain, execution history, displayed state, and persisted chain before the executor rejected it because another execution was already in progress.

    The public initContract() catches the busy error instead of propagating it. Its cleanup also sets executingOperation to null while the original execution is still pending.

    The resulting behavior depends on the original execution:

    • If it succeeds: the chain and history are restored, but isContractInitialized remains false, preventing subsequent triggers.
    • If it fails: the chain and displayed state remain cleared.

    I reproduced this with deterministic deferred promises across both execution modes.

    This appears separate from #1107, which focuses on restart confirmation. The concurrency guard needs to reject the competing initialization before it mutates execution state.

    No repository source or test files were modified during this investigation.

  9. coinjanet5-source commented on Nov 20, 2026

    @coinjanet5-source

    Hi! I work with supplier and service agreements, engineering procurement, and tender documentation. I’d be happy to help test Design V2 manually from a contracts user’s perspective.

    I can walk through a sample template using fictional data, check whether the steps and validation messages are clear, and report any reproducible issues with steps, expected vs. actual behaviour, and browser/OS details.

    Is there a particular template or workflow you’d like me to test?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedExtra attention is neededmaintainer-engagedA maintainer has commented or reviewed this item

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions