Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support "mandatory" constraint for "StringCombo" control #6

Open
sanak opened this issue Mar 8, 2023 · 2 comments
Open

Support "mandatory" constraint for "StringCombo" control #6

sanak opened this issue Mar 8, 2023 · 2 comments

Comments

@sanak
Copy link
Contributor

sanak commented Mar 8, 2023

From the following issue's comment, supporting mandatory (=disallow empty) constraint for StringCombo control will be preferable.

@moovida
Copy link
Member

moovida commented Mar 8, 2023

Ah, I see, yes. Also the whole mandatory thing needs some revision.

At the moment it is possible to safe the note even if mandatory field are not filled.
Since it is possible to complete the form later in the office, I have never placed that block.
What do you think about that?

@sanak
Copy link
Contributor Author

sanak commented Mar 8, 2023

@moovida (CC: @dkastl, @smellman)
Oh, yes. Just same level constraint as note (string) will be enough, I think.

  • Show ( mandatory ) at right side of the label.
  • If nothing is selected, show red frame to remind to operator.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants