docs: updated the styling ADR to include details about how to work wi… - #362
Conversation
…th MXUI and CSS Modules
Jameson13B
left a comment
Jameson13B
left a comment
There was a problem hiding this comment.
This looks great to me!
codingLogan
left a comment
codingLogan
left a comment
There was a problem hiding this comment.
This should be fine, and I will approve. I'll put my meeting comments here as well though.
What I don't want to happen with this change, is the frustration of feeling blocked, or forced to add more complexity to an otherwise simple and easy-to-review MR.
If there is a clear goal for an MR, and it doesn't strictly adhere to this rule, we should give some leeway if there is a documented goal to keep working in the area. For example, if a Jira ticket is exist to finish the work, and it's not a "someday" kind of Jira ticket. If the ticket is next sprint or right after this one, that's when we could allow a small step toward this.
Sometimes it's easier to work in small iterative steps to avoid conflicts and bloat for reviews, and we shouldn't discourage that way of working for the sake of an ADR, in my opinion.
4 participants
…th MXUI and CSS Modules