What do you think about Status and Categories #5014
NicolasCARPi
started this conversation in
General
Replies: 1 comment
-
Hi Nicolas. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Specifically, do you think it would be important to have a defined set of Status for a given Category?
Currently any Category can be of any Status. When I implemented it first I thought: "Okay and we'll add the possibility to define status per category later on".
But after using it for a while, I find it actually useful to have a single source of Status, whatever the Category is. In my database, my Resources Status are: "Cooking, Active, Inactive, Former". And it works fiiiiine.
If the status are generic enough, such as "Opened" "Closed" "Operational" "Maintenance mode", it works pretty well.
There is also a question about simplicity, both in term of code, but also in terms of user interface. The fact that Status and Category are currently decorrelated and can even be
null
seems to be working fine.So do you think it would be super important to limit some status to some categories, or is the current state good enough?
Beta Was this translation helpful? Give feedback.
All reactions