LivelyKernel / LivelyKernel/lively.morphic
path position initialization
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Looking at https://github.com/LivelyKernel/lively.morphic/blob/master/morph.js#L1724
Why is the position re-set?
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 at morph.js#L1724 and read the surrounding path-position initialization and any nearby callers. Determine why the position is reset and whether the issue requires an explanation, documentation, or a code change; the work is done when that rationale and resulting action are clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100