Repository navigation
docs: use the Format constants in the README convert examples - #31
Merged
Merged
Conversation
The convert examples passed raw media-type strings, so nothing in the README pointed at the constants this release adds. They now use tinify.Format, with a note that the plain strings still work, and the feature list mentions JPEG XL alongside the other convert targets.
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
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.
The convert examples in the README passed raw media-type strings, so the
Formatconstants added in 1.8.0 (#28) appeared nowhere in the README.tinify.Format.WEBP/tinify.Format.AVIF/tinify.Format.JXL, with the full set listed in a comment.type="image/webp"keeps working — nothing here is a behaviour change.Documentation only; no code or version change.
🤖 Generated with Claude Code