DX Custom Rule about ncform HOT 3 OPEN

1. Q：Is there a way to debug dx expressions? I'm happy to figure them out - but find it hard without being able to see them evaluate.
   A: You can use function style of dx to debug the value, refer to https://github.com/ncform/ncform#dx-expression

2. Q: My idea was to use a rule like the example below on each of the 3 fields and to tell each one to fire the other 2 rules, so that they all update at roughly the same time.
   A: Refer to this example: https://codepen.io/daniel-dx/pen/eYBKXVL. But there has some problems:

   1. you must hide the "*" symbol by yourself (may be by overriding the style)
   2. there is a bug that when the required message show and the filed's rule become no required, the required message cannot hide automatically(this i will fix it as soon as possble)

from ncform.

Thanks Daniel!

I totally missed the note about function-style dx expressions - that's really brilliant. Does this mean that the dx-syntax is just there to enable a shorter form for writing very simple expressions or is there a performance penalty in choosing one style over the other? I would imagine the dx-expressions must be slightly slower - since they need to be parsed/processed? (probably not even measurable for most common situations).

I'll leave this issue open until the bug is fixed. If you have another issue tracking the bug - please feel free to close this one.

from ncform.

If you want to pass the schema to server, you can only use the string-style dx.
And if you just write the schema in the code, you can feel free to use the function-style

from ncform.