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
Global Variables #265
Comments
Hi @camilamaia! Can I assign it to myself? |
@gillianomenezes yes sure!! |
Hi. I am trying:
|
@BrunoPontesLira not yet. There is a PR opened for it, but we did not merge it: #328. We need to test it first and ensure it works properly. |
Actually, the PR #328 does not solve it, my bad. It only makes it possible to create vars at endpoint level. This is still an open issue |
I'd like to work on this issue, but since it's a non-simple change I'd like to discuss if you already have an intended approach to solve this problem. I was reading through the yaml specification and it says keys don't have a specific order. Considering that, we couldn't just run request nodes without ordering them. The way I'm thinking to approach the issue is building a dependency graph of request nodes, and we execute nodes without dependencies or with solved dependencies. What are your thoughts? |
Ok, I admit that the first suggestion was the first thought without deeply studying the code hahaha |
Global Variables
Enable the possibility to have global variables. Sometimes we need to access a variable from outside the scope, for example:
It would be nice to have a way to store
book_id
globally. Currently, the example above wouldn't work because the second request is not in the same scope as the first one.The text was updated successfully, but these errors were encountered: