Skip to content
This repository has been archived by the owner on Apr 17, 2023. It is now read-only.

Add inline validation for fields in Namespaces#index form #1376

Closed
vitoravelino opened this issue Aug 8, 2017 · 2 comments
Closed

Add inline validation for fields in Namespaces#index form #1376

vitoravelino opened this issue Aug 8, 2017 · 2 comments
Assignees
@vitoravelino
Labels
enhancement ui ux
Milestone
Release 2.3

Comments

@vitoravelino
Copy link
Contributor

Currently there's no inline feedback validation when for back-end validation. The only way of showing validation is through the floating alert which is not good for this case.
@vitoravelino vitoravelino added this to the Release 2.3 milestone Aug 8, 2017
@vitoravelino vitoravelino self-assigned this Aug 8, 2017
@vitoravelino vitoravelino mentioned this issue Aug 8, 2017
Merged
8 tasks
@mssola
Copy link
Collaborator

mssola commented Aug 9, 2017

The investigation for this can be useful to fix #861 and #1355.

vitoravelino added a commit to vitoravelino/Portus that referenced this issue Aug 22, 2017
@vitoravelino
js: added inline validation for namespace's new form
87797fc 
The validation so far was fully done on the server side and
the feedback was through the float alert that disappears in 5 seconds.
Not the best experience for the users.

Now, for each field (name and team), we have an inline feedback validation.
User will only see a validation message on the float alert in unexpected
situations.

Fixes SUSE#1376
@vitoravelino vitoravelino mentioned this issue Aug 22, 2017
Merged
vitoravelino added a commit to vitoravelino/Portus that referenced this issue Aug 22, 2017
@vitoravelino
js: added inline validation for namespace's new form
9c223b7 
The validation so far was fully done on the server side and
the feedback was through the float alert that disappears in 5 seconds.
Not the best experience for the users.

Now, for each field (name and team), we have an inline feedback validation.
User will only see a validation message on the float alert in unexpected
situations.

Fixes SUSE#1376
@vitoravelino
Copy link
Contributor Author

The investigation for this can be useful to fix #861 and #1355.

It definitely was.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@vitoravelino vitoravelino

Labels
enhancement ui ux
Projects
None yet
Milestone
Release 2.3
Development

No branches or pull requests
2 participants
@vitoravelino @mssola