OSC Command Naming Convention
Registered by
Slade Baumann
In OSC when developers are implementing commands from their
specific project, there are no guidelines or convention for them to follow.
This can potentially cause issues where the user is left confused of what a
command actually does if the developer uses a broad command name.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Slade Baumann
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Slade Baumann
Related branches
Related bugs
Sprints
Whiteboard
Accidentally created this under cinder, so there is an identical one (the real one) that is under python-
https:/
(?)
