fix(issue 256): upload issue with images fix #257
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
neSpecc
reviewed
Jul 17, 2024
neSpecc
reviewed
Jul 17, 2024
neSpecc
reviewed
Jul 17, 2024
neSpecc
approved these changes
Jul 17, 2024
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.
Problem
The issue #256 where the 'files' is used the upload request instead of
imagesin default configuration.Cause
The cause of this issue is when the field in the configuration is not defined by the user, for this reason, the 'files' is used by
ajax.transportby default.Solution
The solution for this issue is to use
imagevalue in config ofImageToolwhen it is not defined by the user.