Meteor-Community-Packages / Meteor-Community-Packages/ground-db
Change in Template level autorun behaviour
- Dominant language
- JavaScript
- Stars
- 569
- Forks
- 77
- PR merge metrics
- No merged PRs in 30d
Description
I encountered some problems with the newest ground:db version related to the dispatch:kernel package (which was introduced in v0.3.9). This package causes template.autorun() to rerun after the view is already destroyed! That is causing various problems in our project, especially with autoform and some own components.
Contributor guide
Research direction
Start by reproducing the behavior with the newest ground:db version and its dispatch:kernel package, focusing on template.autorun() after a view is destroyed. Check the lifecycle around the affected template and verify completion by confirming autorun does not rerun after destruction without causing problems for autoform and custom components.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100