Knockout-Contrib/Knockout-Validation

Improve configuration and initialization

Open

#545 ouverte le 15 févr. 2015

Voir sur GitHub
 (0 commentaires) (0 réactions) (0 assignés)JavaScript (1 024 stars) (394 forks)batch import
enhancementhelp wanted

Description

Currently the library initializes itself - without the need to call ko.validation.init. Also, binding handles like value, textInput etc. are automatically wrapped to become validatable. This adds difficulties in working with libraries like knockout-es5 or to prevent the registration. Furthermore, some may already define extenders which this library registers. Ideally, changes to this feature should not cause any breaking changes.

Related issues: #477 Opt-out option for makeBindingHandlerValidatable #478 Calling ko.validation.group on object makes all observables validatable #404 RegisterExtenders invoked before Init, cannot avoid adding rules to ko.extends #150 Exposing default options #192 Add option asyncOnModified (Related issue #180)

More investigation is needed for the following issues: #540 Support live option for observable objects #49 Changing validation rules on the fly

Guide contributeur

Stack technique
javascript
Domaine
frontend
Type d'issue
refactor
DifficultéDifficulté estimée pour un nouveau contributeur, de 1 pour un très petit changement à 5 pour un travail expert.
3
Temps estiméFourchette de temps approximative pour investiguer, implémenter, tester et préparer une pull request.
over 1 week
Statut d'activitéDisponibilité apparente de l'issue : fraîche, active, ancienne, bloquée ou en attente d'un mainteneur.
stale
ClartéClarté avec laquelle l'issue explique le changement attendu, les critères d'acceptation et la prochaine étape.
mostly clear
Prérequis
familiarity with Knockout.jsunderstanding of validation patterns
Accessibilité débutantScore de 1 à 100 estimant l'accessibilité de cette issue pour un premier contributeur.
20
Direction de recherche
Examine the library's current initialization code (likely in ko.validation.init or similar), the automatic wrapping of binding handlers, and the registration of extenders. Review linked issues #477, #478, #404, #150, #192 for specific opt out and configuration suggestions. Investigate how to make initialization optional and allow users to disable automatic handler wrapping without breaking existing usage. The goal is to preserve backward compatibility while adding flexibility for integration with knockout es5 and custom extenders.