Better tending of the unsubscribe functions #68
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: profectus/Profectus#68
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Give them a property (use a symbol) that letters get recursively checked for upon removal, to make sure the unsubscribe functions get called. Also check that all created unsubscribe functions were added to the layer during it's construction, similar to persistent refs
Actually, if we're connecting them all during layer creation anyways, just assign a property to the layer with all of them automatically. Then the only error we'd need to give the Dev is if they create an unsubscribe function outside of any letter creation.