Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Resurrecting status as an enum #18

Closed
stuartpb opened this issue Jan 21, 2018 · 2 comments
Closed

Resurrecting status as an enum #18

stuartpb opened this issue Jan 21, 2018 · 2 comments
Labels
model / schema Shortcomings of the project definition structure

Comments

@stuartpb
Copy link
Member

This would be an enum to handle the basically-orthogonal-to-stage concerns touching #1, such as retirement (#7) and abandonment (#10).
@stuartpb
Copy link
Member Author

stuartpb commented Jan 21, 2018 •
edited
Loading

See, the thing is, I don't want to go for an outright status enum, because (1) it's kind of confusing to understand in relation to stage and (2) statuses like "merged" (#12) will probably be signified with a dedicated field, so it'd make more sense to have some kind of name that only covers statuses that won't be signified by value-oriented keys.

@stuartpb stuartpb added the model / schema Shortcomings of the project definition structure label Jan 24, 2018
@stuartpb
Copy link
Member Author

The disregard and pass tag lists currently being drafted in #10 seem like a better fit for this.

@stuartpb stuartpb mentioned this issue Jan 27, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
model / schema Shortcomings of the project definition structure
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@stuartpb