This repository was archived by the owner on Jun 30, 2022. It is now read-only.
[NEW] add support for URI data in audio attachments #461
Conversation
This file contains hidden or 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
renatobecker
suggested changes
Aug 4, 2020
Co-authored-by: Renato Becker <renato.augusto.becker@gmail.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
ISSUE
Currently, the Livechat Widget adds the server Url in front to each of the audio attachment URL. Eg. If the audio-attachment URL is
file-uploads/abc/audio.mp4, then the widget converts it tohttp://localhost:3000/file-uploads/abc/audio.mp4.However, this behavior is not required when the data in attachment is in DATA_URI_SCHEMA.
This PR attempts to solve this issue.