Support text-expressions about redux-autoform HOT 8 CLOSED

Actually the possible workaround to use functions is to have the Schema stored in JS file. I mention this as a remember me.

Things that we have to deal with:

• special characters on strings
• define a way to help the metadata processor to recognize normal text vs text expressions

I think that's all..

from redux-autoform.

So, I have the code to do it already. Because it happens to be supported in React-Metaform, which is also mine: https://github.com/gearz-lab/react-metaform

You got the point right! How do we know if a string is an expression?

on React-Metaform, this is how I did this:

{
    required: "_exp:m.value > 3000";
}

The _exp prefix indicates a text expression.

If you don't like it, we can prefix the metadata itself. JS allows two non-[a-z] characters to start a string: _ and $. RAF uses $ already to denote a lazy function. That is, a function that shouldn't be evaluated, but rather passed to the component. We're left with _. So... You pick.

from redux-autoform.

I can solve this one fairly easily. I just didn't finish this one today because I got the password problem to solve which I did.

from redux-autoform.

@andrerpena how are you going with this? Do you need some help?

from redux-autoform.

In metadata properties starting with $ functions are not supposed to be
evaluated so yes.. You are supposed to be able to pass functions to your
components

Em 22 de ago de 2016 23:42, "Daniel Gómez" [email protected]
escreveu:

Hey @andrerpena https://github.com/andrerpena !! So using the $ i can
pass a function to a component???, i'm having troubles passing functions to
the WizardGroup, it's wierd that in the demo is working but no in the
project i'm doing.... :/

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#71 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABghdZap0M57GBNV053K-egrrxz1WWGDks5qil4TgaJpZM4JoAM5
.

from redux-autoform.

Ok, this is good! So this issue can be closed?

from redux-autoform.

If there's not a confirmed bug then yes, this should be closed. I didn't test it again though

from redux-autoform.

Ok, I will close it! If we have a trouble we will reopen it

from redux-autoform.