pull down to refresh

0 sats \ 3 replies \ @jeff 24 Apr 2022 \ parent \ on: Daily discussion thread
This language pops up...
must be at least 1000
...and it goes red. Unless you remove it completely. Kind of non-standard, or just oddly subjective UX, IMO.
I couldn't reason about why the choice would be from the set {0, 1000, 1001, 1002, ...}. I would have expected any positive integer if it was actually optional.
write
preview
0 sats \ 2 replies \ @k00b 24 Apr 2022
Hmmm I can see why that'd be confusing. I'm just not sure how to design it otherwise. Any ideas?
reply
1050 sats \ 1 reply \ @jeff 24 Apr 2022
...right now, you kind of have like a Schrödinger-cat equivalent of a None/Zero.
Maybe subtle change to the form validation logic:
Current:
  • {Negative Integer} -> Red -> "must be at least 1000"
  • {None} -> Yellow -> lets you post
  • {0, ..., 999} -> Red -> "must be at least 1000"
  • {1000, ...} -> Yellow -> lets you post
Proposed:
  • {Negative Integer} -> Red -> "must be 0 or at least 1000"
  • {None, 0} -> Yellow -> lets you post
  • {1, ..., 999} -> Red -> "must be 0 or at least 1000"
  • {1000, ...} -> Yellow -> lets you post
reply
0 sats \ 0 replies \ @k00b 24 Apr 2022
Ah I get it! I just need to say 0 is allowed!
reply