Comments (5)
Hi, I think you're quite close, it's just a question of precedence and parenthesis now. I got it working with this adaptation of lib's example:
validate : Validation CustomError User
validate =
map8
User
(field "name" (string |> andThen nonEmpty))
(field "email" (email |> andThen (asyncCheck True)))
(field "password" (string |> andThen (minLength 4)))
((field "password" string) |> andThen validateConfirmation)
(field "admin" (bool |> defaultValue False))
(field "date" date)
(field "profile" validateProfile)
(field "todos" (list validateTodo))
validateConfirmation : String -> Validation CustomError String
validateConfirmation password =
field "passwordConfirmation"
(string
|> andThen
(\confirmation ->
if password == confirmation then
succeed confirmation
else
fail (customError ConfirmationError)
)
)
That could be better, I'm trying to create a helper that would enable us to write field "passwordConfirmation" string |> andThen (confirm "password")
from elm-form.
Hi,
Thank you for the great works, this library helped me so much since I need to write a lot of forms views...
While working with this validation example, I noticed it was not trivial to show user friendly error messages. Adding |> withCustomError
at the end of password
validation does not show the expected message but InvalidString
or Empty
depending on the initial edit or not. This annoying behavior may be caused by the validation error from (field "password" string)
on the next line which has a higher priority than custom errors.
Anyway I figured out a workaround and so wanted to share it.
Simplified original example: Code on Ellie
validate : Validation String User
validate =
succeed User
|> andMap (field "name" (string |> withCustomError "Input Name !"))
|> andMap (field "password" (string |> withCustomError "Input Password !"))
|> andMap ((field "password" string) |> andThen validateConfirmation)
validateConfirmation : String -> Validation String String
validateConfirmation password =
field "passwordConfirmation"
(string
|> andThen
(\confirmation ->
if password == confirmation then
succeed confirmation
else
fail (customError "Confirmation Error")
)
)
Example with user friendly error messages: Code on Ellie
validate : Validation String User
validate =
succeed User
|> andMap (field "name" (string |> withCustomError "Input Name !"))
|> andMap (field "password" (string |> withCustomError "Input Password !"))
|> andMap
(oneOf
[ (field "password" string) |> andThen validateConfirmation
, emptyString |> andThen validateConfirmation
]
)
validateConfirmation : String -> Validation String String
validateConfirmation password =
field "passwordConfirmation"
(string
|> withCustomError "Input Password Confimation !"
|> andThen
(\confirmation ->
if password == confirmation then
succeed confirmation
else
fail (customError "Confirmation Error")
)
)
from elm-form.
I have done some further troubleshooting and it seems that reading 2 different fields as I had shown above does not make it possible to track the error in the field's error state. One field is nested into another and the error states are not updated at all when validating the fields.
We may have to look into another way of solving this issue.
I will appreciate your comments.
from elm-form.
Great stuff @etaque.
This works!
Many thanks.
from elm-form.
This was genuinely helpful. I found this thanks to the help from david_hernandez on slack. Maybe this should be part of some example or in the Readme as this serves as a simple example of interdependent validation.
from elm-form.
Related Issues (20)
- Nesting a multiple field validation loses the error HOT 2
- Initial textarea value on IE does not work HOT 3
- Example code typo in README
- Support for Ints? HOT 2
- validation it kick off onBlur for initially empty values HOT 1
- Providing default values to nested records?
- How to validate input1 value is the same as input2 value HOT 1
- Email validator too permissive? HOT 2
- Custom Error after validating through an API
- Why is "elm-test" a dependency? HOT 2
- Why no Form.Cancel message?
- Validation error doesn't appear under `liveError`
- Ability to persist form state as JSON ?
- Dependency on elm-test causes compatibility error HOT 1
- Exception Thrown in Output. ReferenceError: Elm is not defined
- Extend Form.Input to support date input
- Example does not compile (Elm 0.19.1)
- Update to `elm-explorations/[email protected]`
- Form Input maintained on Reset HOT 2
- Form validation for more than 8 fields? HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from elm-form.