Sanitize Reserved Queue Metadata
Registered by
Kurt Griffiths
Whenever we add a special _name field to queue metadata, we need to add safeguards or sanitization migration scripts to avoid crashing and burning in case of a name collision with a user's custom field (even though we told them names starting with underscores are reserved!)
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Kurt Griffiths
Related branches
Related bugs
Sprints
Whiteboard
Since _names are reserved, there is no such thing called "custom fields"; we can just say.... "unused reserved fields" :)
(?)
