-
-
Notifications
You must be signed in to change notification settings - Fork 104
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
Add root level variables
option
#122
Conversation
variables
optionvariables
option
And as for item-level variables, I think we don't need additional work because we can handle it by the present's code. If you don't think so, or there is something we need to do, pls let me know. |
I think you need to put some more work into the docs. |
Thank you for your feedback. I've added some info about item-level variable. |
Do we still need more work about docs? If so, could I get some hints about what should be included in the document? |
@stdavis If you need this, help reviewing this PR is welcome :) |
This still applies. |
I've added an example (email-validate) using root-level To prevent unnecessary complexity of README, the email-validate example excluded logic to determine whether the input is the valid email by regex. In fact, the screenshot I just uploaded doesn't look good. But, I updated this because I want to know whether this example explains enough how to use variables. I would appreciate it if you let me know if this example still doesn't explain enough how to use variable to users. |
To be honest, I don't have an idea about how to reinforce the document. |
I appreciate the effort, but it's simply not close to being mergeable and I don't currently have the time to clean it up. |
Related Issue
Fixes #43
Usage
Test
Here is test code.
And this is the debug log.
I logged
{var:apiKey}, {allVars}
.You can check variables property works by the above test log.
Please let me know if there's anything lacking.