Task: API for saving images

[letsintegreat]

In order to implement the insert image feature in description formatting, create an API which will accept an image and return its URL.

[Yashsomalkar]

But we are already having a select image functionality, right ?

[letsintegreat]

But we are already having a select image functionality, right ?

As we have now introduced GFM, it gives users the ability to insert images right into the description. So, they can decide on the location of the image in the text, which was not possible before.

The functionality will be similar to GitHub's markdown, when an image is inserted, it is sent to the backend, and the image is embedded via its URL, like this -

![ALT_TEXT](URL)

[Yashsomalkar]

But we are already having a select image functionality, right ?

As we have now introduced GFM, it gives users the ability to insert images right into the description. So, they can decide on the location of the image in the text, which was not possible before.

The functionality will be similar to GitHub's markdown, when an image is inserted, it is sent to the backend, and the image is embedded via its URL, like this -

![ALT_TEXT](URL)

Ahh awesome

[AtmegaBuzz]

@letsintegreat best is create a form data and send images with it, in backend you can make description as RichTextField or any other field which supports markdown characters and then, then create a view with formdata parser to accept the api request in form format, this way you dont have to create another api just for saving images.

Remember this will require change in model, web and app are using same model. let's have a small meet so that we migrate both web and app at same time

[letsintegreat]

let's have a small meet so that we migrate both web and app at same time

Alright, I'd reach out to you on Slack for setting up the meeting, thanks!

[letsintegreat]

@fredfalcon - @AtmegaBuzz and I just had a meeting to discuss how can a user upload an image and display it in the middle of an issue description.

Our first approach was the standard approach used by GitHub and Stack Overflow. Paste an image in the description field, that image will be uploaded to the server and its URL will be embedded in the description via markdown. But the problem with this is that, after pasting an image, the user may choose not to complete the issue report (or the issue is deleted in the future), in that case the uploaded image will keep using resources in our server for no reason.

After a few more rejected approaches, this is what we came up with finally - Let's say the user has upload 5 screenshots, then they can embed those screenshots with a special syntax, let's say $1 and $3. In this way first and third screenshots will be rendered in between the description as specified by the user, and the rest of the screenshots will be rendered, as usual, under the screenshots heading.

What are your views on this? Should we start working on it?

[fredfalcon]

sounds like a good efficient solution maybe [img1] [img2] or something

[AtmegaBuzz]

cool then lets go with $ [img1] $ [img2] or [img1] [img2], cause $3 can be used to mention currency by the reporter

[Atharva-Kanherkar]

Can i start working on this issue?

[DonnieBLT]

You can self assign by typing / assign (together)

[Atharva-Kanherkar]

/assign

[nick2432]

/assign

[github-actions]

You are already assigned to another open issue, please wait until until it's closed or remove your assignment to get assigned to this issue.

[kr-2003]

@DonnieBLT
I want to work upon this issue. I just want to ask that BLT stores media files in /media folder directly into the server, right?
So, the api should return the local path of the image from /media folder, when uploaded, and not from any cloud storage like S3.

[kr-2003]

cool then lets go with $ [img1] $ [img2] or [img1] [img2], cause $3 can be used to mention currency by the reporter

@DonnieBLT I am gonna go with this approach.

[DonnieBLT]

Sounds good

[kr-2003]

/assign