Events need consistent naming conventions #1746
Labels
D: easy
Straightforward issues, small time commitment
I: minor
Low, impact, low priority bugs
T: enhancement
Adding additional functionality
Milestone
General housekeeping task.
The way events have been named is often overly verbose, not always self-evident, and often inconsistent. Some examples:
location:title:update
could just belocation:setTitle
remove:views
- we generally use the structureMODULE:ACTION
, soorigin:removeViews
or justorigin:remove
seems more logicalThe first step is probably to document all events in the system, and decide a sensible structure from there.
The text was updated successfully, but these errors were encountered: