search

eurofurence / crittersystem

Shift planning system for Eurofurence on-site departments forked from the Engelsystem which powers Chaos events.
https://critter.eurofurence.org
GNU General Public License v2.0
8 stars 1 forks source link

Communicate Nickname restrictions better #31

Closed KiraResari closed 2 months ago

KiraResari commented 2 months ago

Is your feature request related to a specific event or situation at Eurofurence?

No

What problem are you trying to solve with this feature?

I tried entering my nickname as "Kira Resari" because the "Nick" field did not communicate any restrictions. Then I got an error saying "Please enter a valid nick:Use up to 24 letters, numbers or connecting punctuations (.-_) for your nickname." While I do understand that this implies that spaces are not allowed, it would be better if the field clearly communicated this.

Describe the solution you'd like to see implemented

Ideally, the field would have a real-time validator that checks the entered nickname and if an invalid character is entered communicates this specifically, like "Invalid character: '%'" or "Spaces are not allowed.

A more pragmatic solution would be to add this either as a tooltip, or in the field description: "Nick (numbers, letters, and . _ - no spaces allowed)"

How would this feature improve the Critter System for Eurofurence volunteers or attendees?

Usability & accessability

RustyBraze commented 2 months ago

To be looked

Corborax commented 2 months ago

It's actually a good point. Limitations should be communicated.

The space may cause issues in the legacy code of the critter system. Quickfix should do it.

  1. Maybe it's an option to replace | |<- spaces with . if someone wants a spacing in their name?

==> Blue.Wolf instead of Blue Wolf.

  1. Or we just keep the notification in place and just add the tooltip / info on the page, that spaces are not allowed.
RustyBraze commented 2 months ago
  1. Or we just keep the notification in place and just add the tooltip / info on the page, that spaces are not allowed.

This would be the best option. Automatic conversion usually cause unwanted results

Corborax commented 2 months ago

Was revolved with https://github.com/eurofurence/crittersystem/pull/53