Extending contentCreate() to fetch files from remote URL #19
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
contentCreate by default, only supports local file paths in order to create a file object which can be sent as a message in sparky bot. Using request and buffer libraries, a new functionality has been added that enables us to create File Objects can from a remote URL path, which should come very handy to directly send the files without ever needing to perform disk operations (reads/writes) of any kjnd.
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.
contentCreate() by default, only supports local file paths in order to create a file object which can be sent as a message in sparky bot. Using request and buffer libraries, a new functionality has been added that enables us to create File Objects from a remote URL path, which should come very handy to directly send the files without ever needing to perform disk operations of any kind, at the server end.