Update Colours For Review Status (Take Two) #175
Reference in New Issue
Block a user
Delete Branch "review-status-colours"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Supersedes #171.
This rebases onto staging branch, fixes up the status ids, and copies the colors over to mapfixes.
Would suggest standardizing on the material ui colors (success, warning, failed, primary, secondary) and then changing those in the theme if desired vs going around the ui framework. Don't think we need a bunch of different shades either.
Could be as simple as:
Failed: The map was rejected
Success: Final state(s)
Info (blue): Any transition state
Warning: Any state requiring interaction
Where each state falls to is up for debate though.
this seems like a pretty simple solution. my only gripe would be where like changes requested or accepted, not validated would come under, since they could be considered to be in 2 states at the same time (failed but warning, success but warning).
Changes Requested = Warn, Interaction Required (by Submitter)
Accepted, Not Validated = Warn, Interaction Required (by Quat)
I'll be coming back through and re-doing the whole submission/map fix page so maybe this holds off until then? We can still standardize the colors/state names though.
Done in #183
@numberss yell at me if you don't like them
Pull request closed