-
-
Notifications
You must be signed in to change notification settings - Fork 27
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
Documentation for input binding/validation #54
Comments
I'm sorry about the missing gist.run here is an updated one https://gist.run/?id=6e5d8a599932dcdd04f4363c7c731a1a |
@zewa666 Thanks for adding that! Seems aurelia-validation is still missing from that bundle. Are you able to easily add that in since the issue I am experience is dependent on the interaction between store/validation. |
@jordanmaslyn updated the gist with Aurelia Validation + Aurelia I18N |
@zewa666 I've made some progress at https://gist.run/?id=d7171f9290bb9d777399b0b65ab345b9 but if you look at the console, you'll see an error that looks like it might be related to aurelia/validation#350 where I can't use the validate binding-behavior. This is resulting in the validation renderer receiving no elements. |
@jordanmaslyn @zewa666 It is indeed this error: aurelia/validation#350 (comment) |
@zewa666 Is that something you are able to fix from your bundle? |
@zewa666 I can see in your package-lock that there's a few |
Will try to resolve that this week |
updating the dependencies to get rid of aurelia-binding v1 issue related issue #54
I've updated the master with cleaned up dependencies. @jordanmaslyn can you try to do the following:
|
Hi there, forgive me if this is the wrong mode for requesting this, but here goes:
My team is in the process of implementing Aurelia Store throughout several of our apps, however we are having troubles with "best practices" in terms of inputs and validation.
It seems like the best practice for a text input would
value.to-view="state.textValue"
and thenchange.delegate="updateTextValue($event)"
, whereupdateTextValue
dispatches the requisite action.Where we are having issues though is that some of our inputs are nested within an array. For example, we have an array of
clients
and we loop through those withrepeat.for="client of state.clients"
and then have a field to change a given property of each client (e.g.value.to-view="client.email"
) .However, when the state observable refreshes, the repeat.for updates and wipes out any error messages/classes created from the ValidationRenderer results.
I wanted to create a reproduction but it appears the gistrun doesn't offer aurelia-store yet. Any thoughts? Is there a better way to accomplish this?
The text was updated successfully, but these errors were encountered: