Support image[] parameter for /v1/images/edits#2321
Open
sagebind wants to merge 2 commits into
Open
Conversation
github-actions
Bot
added
area::api
Author
|
I was able to test a build of this branch on my local setup with Open WebUI, and was able to confirm that this allows image edit tool use in Open WebUI to be compatible with Lemonade, fixing #1963. Here's a screenshot of an example chat in Open WebUI, with LLM, generate, and edit all using Lemonade: 
|
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.
Some clients may send the image to be edited to the image edit API using the conventional (but not strictly standard)
[]suffix to indicate an array of field values in the form, meaning the actual form field name will beimage[]instead ofimage. OpenAI has an example accepting this, and Open WebUI does this explicitly.To make the Lemonade equivalent endpoint more compliant and compatible, it should also accept the image using this naming syntax, even if it currently does not support more than one image, because some clients always use this naming even when sending only one image to be edited.
Fixes #1963