LivelyKernel / LivelyKernel/lively.morphic
Part loading can overwrite old part classes
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
as reported by Robin:
Loading a part of an older version forces the class of it into the system and overrides newer versions.
Fix: Support first class part versions.
Part 1: Each part has a semver major.minor.patch version specifier. Publishing increases the version automatically.
Part 2: Support versions when importing packages (via lively.modules). Sth like `import x from "package@1.2.3/some-module.js"` or `import x from "package@>=1.2.3/some-module.js"`. This can be used by the parts and serialized objects to specify which version of the package they actually want. Multiple versions can then live side-by-side inside the runtime.
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
Start by tracing how parts are loaded and how package imports are handled through lively.modules; the issue provides no file or test path. Compare the requested semver behavior for publishing, imports, parts, and serialized objects, and consider the work complete when older and newer package versions can coexist without overwriting classes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100