Conversation
3ebb0b1 to
368d515
Compare
|
one thing i'm not sure about is style, when on cooldown i've added a disabled attribute on both inputs, but idk if there's a specific style convention you use to visually determine a field as disabled? |
|
i've added a haven't bound to (updated pr's desc to show the new result) |
|
If we're even considering this, the cooldown should be more like 1 year. Or maybe a store purchase. |
|
if so then either cooldown or store purchase should also apply to creating a team to make it fair, right? but this doesn't really seem like a good idea considering teams are only a social feature i guess 2 possible options could be:
|
fixes #12548
i tried to tackle this one with basic features:
name_changed_attimestamp field in team's modelinput-text--disabledcss class