docs: fix incorrect image compression examples in README#351
Open
akhil-ge0rge wants to merge 1 commit intofluttercandies:mainfrom
Open
docs: fix incorrect image compression examples in README#351akhil-ge0rge wants to merge 1 commit intofluttercandies:mainfrom
akhil-ge0rge wants to merge 1 commit intofluttercandies:mainfrom
Conversation
Updated the README image compression examples to match the current API signatures and return types. - Fixed incorrect return types for compressWithFile and compressAndGetFile - Updated file-based examples to handle nullable results correctly - Corrected XFile usage where File was previously assumed - Ensured examples compile correctly with null safety enabled No behavior or logic changes were introduced — documentation-only fix.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Updated the README image compression examples to match the current API signatures and return types.
No behavior or logic changes were introduced
documentation-only fix.
Closes #337