Input field needs validation about web-components

[irmerk]

It should be stored on some state above cicero-ui and passed down through props.

[jeromesimeon]

Would this issue overlap with / be partially resolved by
accordproject/concerto#160 addressing accordproject/concerto#157
?

[jeromesimeon]

I'm wondering how errors during validation are reported by the Concerto UI. Will it work with the Error logger in Cicero UI?

[mttrbrts]

Will it work with the Error logger in Cicero UI?

That's a great idea. We probably want inline errors for form fields, but having the format compatible with the Cicero UI ErrorLogger makes sense to me.

[jeromesimeon]

Will it work with the Error logger in Cicero UI?

That's a great idea. We probably want inline errors for form fields, but having the format compatible with the Cicero UI ErrorLogger makes sense to me.

Maybe @irmerk can provide suggestions. I think it might mean passing some error function as a prop? Then encapsulating the errors using the standard concerto exceptions.

[irmerk]

The ErrorLogger can take a function for when a user clicks on the individual error (originally for navigation to a clause in a contract, could be to redirect user to the concerto form), but otherwise just takes an error object. Currently it is only looking for modelError or parseError, but could be adapted for a new error.

[jeromesimeon]

The ErrorLogger can take a function for when a user clicks on the individual error (originally for navigation to a clause in a contract, could be to redirect user to the concerto form), but otherwise just takes an error object. Currently it is only looking for modelError or parseError, but could be adapted for a new error.

I think a distinct question is how does the Error logger gets notified of the error in the first place?