-
Notifications
You must be signed in to change notification settings - Fork 760
chore: cleanup config passing to HTML from server #5120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
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:
|
|
Looks good at a high level. Noticed the backward compatibility, nice. Some tests failing, haven't kicked the tires, but looks good otherwise |
|
🚀 Development release published. You may be able to view the changes at https://marimo.app?v=0.13.16-dev4 |
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.
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.
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.
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.
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.
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.
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.
…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.
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