Feat optional input format #520
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
iChristwin
approved these changes
Apr 27, 2024
ppedziwiatr
approved these changes
Apr 29, 2024
|
Thanks for the PR! released in v1.4.41 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull-request resolves #516
It addes a boolean option
inputFormatAsDatato overide the behaviour where a warp interactionInput-Formatdefaults totag, hence allowing the SDK user to setInput-Fomattodatainstead.This is especially useful if the warp interaction data is expected to be consumed by other applications that have no concept of an Arweave tag but could simply make a http GET request to any Arweave gateway to fetch the desire data by its iteraction id.
All else works the same.