Skip to content

Conversation

@adamziel
Copy link
Collaborator

Motivation for the change, related issues

When you edit a Blueprint on a temporary Playground, the URL now stays in sync with your changes. This means you can copy the URL at any point and share it with someone else—they'll see the exact Blueprint you're working on.

The Blueprint is base64-encoded into the URL hash, which keeps it shareable without requiring any server-side storage. The URL only updates when the Blueprint is valid JSON, so you won't accidentally share a broken link mid-edit.

Testing Instructions (or ideally a Blueprint)

  1. Edit a Blueprint on a temporary site
  2. Refresh the page
  3. Confirm your change is visible in the editor

cc @SirLouen

@SirLouen
Copy link
Member

SirLouen commented Nov 28, 2025

Tested

I added some code in a file, (in the theme.json of TT5
Then copy pasted the resulting URL

But the new Playground doesn't preserve the same data

I attach here a demo.

pg2959.mp4

@adamziel
Copy link
Collaborator Author

adamziel commented Nov 28, 2025

@SirLouen This change is for the Blueprints editor, not for the code editor. Was your original intention to preserve the changes made in the code editor?

@SirLouen
Copy link
Member

@SirLouen This change is for the Blueprints editor, not for the code editor. Was your original intention to preserve the changes made in the code editor?

Yes, maybe I explained it wrongly.

@SirLouen
Copy link
Member

SirLouen commented Nov 28, 2025

Now I've tested in the Blueprints editor and its working correctly 👍

But my idea was to preserve the code in the code editor as here is where code-based tests are going to mostly happen.

Anyway editing and saving the URL of a fixed blueprint and future edits is a major step because we won't need to save gists for this purpose.

: vErrors.concat(
validate12.errors
);
);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't the indentation a little messed up here?

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants