Skip to content

Conversation

@mscolnick
Copy link
Contributor

@mscolnick mscolnick commented May 29, 2025

This is a start of removing some of the complexity taken on by passing config via HTML dom elements. This also paves the way to clean up some global state that has leaked over time.

There are some DOM elements still left around, but will handle those in a followup

@vercel
Copy link

vercel bot commented May 29, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
marimo-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 29, 2025 11:54pm

@dmadisetti
Copy link
Collaborator

Looks good at first glance and I see the utility of being able to pass this down. Is it just filename that's left?

AFK but my thought is to:

  • try local islands dev
  • quarto
  • also the marimo edit html functionality

@akshayka
Copy link
Contributor

Looks good at a high level. Noticed the backward compatibility, nice. Some tests failing, haven't kicked the tires, but looks good otherwise

@mscolnick mscolnick merged commit b42afa2 into main May 30, 2025
26 of 37 checks passed
@mscolnick mscolnick deleted the ms/explicit-mount branch May 30, 2025 00:36
@github-actions
Copy link

🚀 Development release published. You may be able to view the changes at https://marimo.app?v=0.13.16-dev4

manzt added a commit that referenced this pull request Jun 27, 2025
The changes in #5120 removed passing configuration data via HTML DOM
elements. However, the marimo VS Code extension depends on these
DOM-based attributes, leading to a regression.

These changes restore the minimal set of DOM data attributes
(`marimo-version`, `marimo-user-config`, `marimo-server-token`) required
by the extension to function correctly. These additions are marked as
temporary and should be removed once the extension is updated to no
longer rely on them.
manzt added a commit that referenced this pull request Jun 27, 2025
The changes in #5120 removed passing configuration data via HTML DOM
elements. However, the marimo VS Code extension depends on these
DOM-based attributes, leading to a regression.

These changes restore the minimal set of DOM data attributes
(`marimo-version`, `marimo-user-config`, `marimo-server-token`) required
by the extension to function correctly. These additions are marked as
temporary and should be removed once the extension is updated to no
longer rely on them.
manzt added a commit that referenced this pull request Jun 27, 2025
The changes in #5120 removed passing configuration data via HTML DOM
elements. However, the marimo VS Code extension depends on these
DOM-based attributes, leading to a regression.

These changes restore the minimal set of DOM data attributes
(`marimo-version`, `marimo-user-config`, `marimo-server-token`) required
by the extension to function correctly. These additions are marked as
temporary and should be removed once the extension is updated to no
longer rely on them.
manzt added a commit that referenced this pull request Jun 28, 2025
The changes in #5120 removed passing configuration data via HTML DOM
elements. However, the marimo VS Code extension depends on these
DOM-based attributes, leading to a regression.

These changes restore the minimal set of DOM data attributes
(`marimo-version`, `marimo-user-config`, `marimo-server-token`) required
by the extension to function correctly. These additions are marked as
temporary and should be removed once the extension is updated to no
longer rely on them.
manzt added a commit that referenced this pull request Jun 28, 2025
The changes in #5120 removed passing configuration data via HTML DOM
elements. However, the marimo VS Code extension depends on these
DOM-based attributes, leading to a regression.

These changes restore the minimal set of DOM data attributes
(`marimo-version`, `marimo-user-config`, `marimo-server-token`) required
by the extension to function correctly. These additions are marked as
temporary and should be removed once the extension is updated to no
longer rely on them.
manzt added a commit that referenced this pull request Jun 28, 2025
The changes in #5120 removed passing configuration data via HTML DOM
elements. However, the marimo VS Code extension depends on these
DOM-based attributes, leading to a regression.

These changes restore the minimal set of DOM data attributes
(`marimo-version`, `marimo-user-config`, `marimo-server-token`) required
by the extension to function correctly. These additions are marked as
temporary and should be removed once the extension is updated to no
longer rely on them.
akshayka pushed a commit that referenced this pull request Jun 28, 2025
Fixes #5428 

The changes in #5120 removed passing configuration data via HTML DOM
elements. However, the marimo VS Code extension depends on these
DOM-based attributes, leading to a regression.

These changes restore the minimal set of DOM data attributes
(`marimo-version`, `marimo-user-config`, `marimo-server-token`) required
by the extension to function correctly. These additions are marked as
temporary and should be removed once the extension is updated to no
longer rely on them.
sebbeutler pushed a commit to sebbeutler/marimo that referenced this pull request Jul 7, 2025
…o-team#5480)

Fixes marimo-team#5428 

The changes in marimo-team#5120 removed passing configuration data via HTML DOM
elements. However, the marimo VS Code extension depends on these
DOM-based attributes, leading to a regression.

These changes restore the minimal set of DOM data attributes
(`marimo-version`, `marimo-user-config`, `marimo-server-token`) required
by the extension to function correctly. These additions are marked as
temporary and should be removed once the extension is updated to no
longer rely on them.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants