SmartClient Version: SNAPSHOT_v13.1d_2024-09-06/Enterprise Development Only (built 2024-09-06)
Hello, please modify the FSdmiValidation sample like this:
then, without choosing an item, type 999999 as a quantity, and press "validate". You'll see a validation request (due to the serverCustom validator for "quantity"), and a "Field is required" hover:
then, try the same sample in a different locale, in my case locale=it, and you'll see both the client (localized) message, and the server (not localized) message for the same validation error:
I just want to check with you if it's expected or is a bug or something that you plan to enhance in the framework. I suspect that this wouldn't happen if also server-side messages were localized.
Also I want to ask if stopIfFalse is meant to work also for serverCustom validators, ie if I had 2 serverCustom validators and the first has stopIfFalse, then the 2nd doesn't execute if the first fails. Currently it doesn't seem so.
Hello, please modify the FSdmiValidation sample like this:
Code:
isc.DynamicForm.create({ ID:"testForm", top: 50, dataSource:"validationDMI_orderForm", fields: [ { type:"header", defaultValue:"Add an item to your Order" }, { name:"itemId", title:"Item", editorType:"ComboBoxItem", optionDataSource:"StockItem", valueField:"id", displayField:"description" }, { name:"quantity", validateOnExit:true }, { name:"instructions", editorType:"TextAreaItem" } ] }); isc.IButton.create({ title: "validate", autoFit: true, click: function () { testForm.validate() } })
then, try the same sample in a different locale, in my case locale=it, and you'll see both the client (localized) message, and the server (not localized) message for the same validation error:
I just want to check with you if it's expected or is a bug or something that you plan to enhance in the framework. I suspect that this wouldn't happen if also server-side messages were localized.
Also I want to ask if stopIfFalse is meant to work also for serverCustom validators, ie if I had 2 serverCustom validators and the first has stopIfFalse, then the 2nd doesn't execute if the first fails. Currently it doesn't seem so.
Comment