Events system #2
Labels
No labels
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
Reviewed/Confirmed
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Status/Abandoned
Status/Blocked
Status/Need More Info
Outtakes/Blog Post
Outtakes/Research
Outtakes/Resource
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Severity
Critical
Severity
High
Severity
Low
Severity
Medium
Status
Abandoned
Status
Accepted
Status
Blocked
Status
Need More Info
Status
Out Of Scope
Status
Pending
Status
Won't do
Type
Bug
Type
Documentation
Type
Feature
Type
Idea
Type
Testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: alecodes/fuuka#2
Loading…
Add table
Add a link
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?
Have an event system with the "observable pattern" so it's easier to add/remove functionallity in certain heave tasks, like file system indexation.
User arr's suite as an example.