Knockout-Contrib/Knockout-Validation

Improve displaying of validation message

Open

#542 opened on Feb 10, 2015

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (1,024 stars) (394 forks)batch import
enhancementhelp wanted

Description

The validation message must be improved to enable some features that were frequently asked:

  • Different position in DOM of the validation message / message template
  • Enable validation message / message template animation when observable transitions from valid to invalid state and viceversa
  • Enable different ways of showing the validation message (data-xxx attributes, custom methods - eg. QTip, toasts etc.)

If more improvements should be made, leave a comment and I'll update the list.

Related issues: #260 Showing validation message on popup #238 Qtip with Knockout-Validation #348 Custom position to messageTemplate #410 Custom method to display error message #456 Placing custom validation template #432 Allow alternative means of hiding/showing error message. #302 Error messages from data-val-xxx attributes

Contributor guide

Tech stack
javascript
Domain
frontend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
KnockoutJSKnockout ValidationDOM manipulation
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
The issue requests multiple enhancements to the validation message display. To begin, review the current implementation in the source code, particularly files related to message templates and validation binding. Examine the linked issues (#260, #238, #348, #410, #456, #432, #302) for specific use cases and community feedback. Consider providing a comment to ask for clarification on priority or acceptance criteria before implementation.