-
Notifications
You must be signed in to change notification settings - Fork 72
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
Widen allowed HTTP parameters #1797
Conversation
5cd83d3
to
d2035f9
Compare
d2035f9
to
874f9c4
Compare
@api3/ois has been published and references updated in this branch. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! And thanks for testing, I'll go ahead and merge. Note I added one commit to bump Airnode's zod version to match that of OIS's zod version given multiple zod versions have been a problem before.
Ah yes I’ve come across that too @ multiple Zod versions. Thanks for sorting out/merging :) It might be worth asking the original issue reporting user to test the latest docker preview builds? |
* Widen parameter type * Fix validation tests * Update @api3/ois fixtures * Bump zod to match zod version in @api3/ois v2.1.0 --------- Co-authored-by: Derek Croote <[email protected]>
Closes #1790
Relates to this thread on Slack.
This PR widens the type of allowed fixedOperation parameters and HTTP call parameters that can be used in Airnode.
This PR goes hand-in-hand with api3dao/ois#88
This allows a user to configure Airnode, either via a fixedOperationParameter or via pre-processing, to send a set of complex or non-string parameters to the remote API. The user's use case was to embed an array containing a
false
element in the JSON payload POSTed to an EVM node.The OIS package will be swapped for the real package once the OIS PR is approved and package published.
I have tested these changes via the HTTP gateways. The test configuration can be found in the Slack thread^
Example from config.json: