Skip to content
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

Add ability to send back diagram image to server #45

Open
dangunter opened this issue Feb 2, 2024 · 2 comments · May be fixed by #51
Open

Add ability to send back diagram image to server #45

dangunter opened this issue Feb 2, 2024 · 2 comments · May be fixed by #51
Assignees
Labels
Priority:Normal Normal Priority Issue or PR

Comments

@dangunter
Copy link
Member

dangunter commented Feb 2, 2024

Add ability to send back diagram image to server through FastAPI

an API call to Jupyter Notebook like,

fv = model.visualize(...)
fv.save_diagram(file=.. or display=True)
# if display=True, return value displays in Jupyter notebook
@ksbeattie ksbeattie added the Priority:Normal Normal Priority Issue or PR label Feb 8, 2024
@ksbeattie ksbeattie added Priority:Low Low Priority Issue or PR and removed Priority:Normal Normal Priority Issue or PR labels Mar 14, 2024
@CopyDemon
Copy link
Contributor

now we don't have fastapi server but will work this with http server

@CopyDemon
Copy link
Contributor

this ticket addressed by PR 51

Working in progress, bug shows up returned image size is odd, working on fix that.

@ksbeattie ksbeattie added Priority:Normal Normal Priority Issue or PR and removed Priority:Low Low Priority Issue or PR labels Sep 5, 2024
@ksbeattie ksbeattie changed the title Add ability to send back diagram image to server through FastAPI Add ability to send back diagram image to server Oct 24, 2024
@ksbeattie ksbeattie linked a pull request Oct 24, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority:Normal Normal Priority Issue or PR
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants