LivelyKernel / LivelyKernel/lively.modules
constructor without super call not removed
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 8
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
bug reports in german!
1. subclasse mal einen morph und überschreibe den constructor ohne super zu rufen. 2. speicher das module. 3. lösche den constructor wieder. 4 -> jetzt wird, obwohl der constructor gar nicht mehr überschrieben sein sollte, der fehlerhafte constructor immer noch aufgerufen
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 reproducing the reported sequence in the lively.modules module system: subclass a morph, override its constructor without calling super, save the module, then delete the constructor. Done means the deleted constructor is no longer invoked and the erroneous missing-super behavior no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100