-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Image Editor] Implement backend endpoints for MiniPaint #638
Comments
I would say 1. should stay in the UI bundle as it is UI related and not an API topic. But we need an endpoint to be able to save the edited image: |
@ValeriaMaltseva @markus-moser
|
@lukmzig Thanks a lot, but regarding 2 - we would need a stream of the binary content of the asset not the json. |
@lukmzig Thanks! 😊 |
@markus-moser @ValeriaMaltseva I added new endpoint now which returns the binary stream of the original asset based on the ID |
Currently, we have a fake implementation in the controller for the MiniPaint image editor. We need to replace these temporary actions with actual backend endpoints that will handle requests for working with images in the MiniPaint image editor.
Current implementation:
Need:
The text was updated successfully, but these errors were encountered: