Obligate "live" coding for Public notebooks
Describe the bug Once a notebook is set to Public, any change made to a notebook is immediately reflected on the client's side.
To Reproduce Steps to reproduce the behavior:
- Go to https://observablehq.com/@<my_account>
- Click on Notebooks
- Click on New+
- Use Blank template
- Change visibility to "Public"
- Open "Incognito" browser window (or equivalent)
- Navigate to notebook's public URL
- Observe changes being made live
Expected behavior Edit and refactor notebooks without interrupting end-user's experience. Specifically, a way to develop that does NOT obligate I force these items on users
- Bugs
- Incomplete work
- Prototype implementations
- Breakages which occur as part of normal development cycles
Screenshots Not applicable.
Desktop (please complete the following information): Not applicable.
Smartphone (please complete the following information): Not applicable.
Additional context The choice between 💩 on my user's experience and creating a service outage is not one I'm willing to accommodate or endure.
We are working on some options to create a different workflow for this.
Please have a look at the feature called 'pausing live edits'. https://observablehq.com/@observablehq/pause-live-edits-in-public-notebooks Hopefully that addresses this request! If not, please let us know and we can re-open this issue.