LivelyKernel / LivelyKernel/lively4-core
Scripts not stored across page reloads
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 89
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
- Create a view and a derevied view with any data.
- Reload the page.
- Create a new view with any data and drag that data onto the first view.
- An error happens (`vivideLayer.objects is not iterable`) and, while the new seems to connect to the first one (Halo shows the connection), no data is shown in the first view.
- changing the selection of the new view results in further errors (`Cannot read property 'Symbol(Symbol.iterator)' of undefined`)
We definitely need this feature when storing VivideViews as html for reuse.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the reload scenario by creating a view and derived view, reloading, then dragging data from a new view onto the first. Trace VivideView persistence and reload handling around the reported iterable errors; done means stored views can be reused after reload, connections remain valid, and data appears without follow-up errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100