write code to process and save the comma separated frames for a policy issue entered by a user in frontend and backend about openframing HOT 7 CLOSED

Hi @monajalal , the backend doens't need to do this as the JSON API specifies that it will receive a list, not a string. I believe @edward-edberg did manage to split a string into a list in the frontend, but he should be the person to ask here.

from openframing.

Hi Mona,

I'm not sure why we'd be sending a comma separated string to the backend. As we discussed in the meetings before, JSON supports a list type, and I don't see any reason not to use a JSON list. In fact, to use a comma separated string instead of a JSON list appears to me to be confusing to future developers on this codebase.

from openframing.

We have to think about the user in the first place and what would be easier for them to input. Do you have a suggestion for a different sketch and could you maybe draw it with pen on the paper so I can have a look at your idea? @davidatbu

from openframing.

Hi Mona, it's totally fine if the user enters the input as a comma separated list if you think that would be best. Personally, I think that's just fine for now.

But, when that information is sent to the backend as JSON, that string needs to be "broken up" into a JSON list(by using something like string1.split(',') in javascript).

from openframing.

Hi Mona, to be more explicit, if the frontend sends the category_names as a JSON list(which I think is the right thing to do) then this Github issue is unnecessary. Not sure why you labelled it "high-priority" just now ...

from openframing.

is it done, right @davidatbu or @edward-edberg ?

from openframing.

Closing as this is self-evidently done because we can train classifiers using the frontend.

from openframing.