Switching to editing tab on posts/comments causes 422

[joshsmith]

Switching to the editing tab on posts/comments causes a 422 error and "Loading preview..." to render. We should maybe not send the body at all in this case and just render a blank preview.

[begedin]

There should not be a validation error here at all. Did you test it with the correct API branch?

If so, then there's an issue somewhere I need to check.

Also, while I'm on it, we should probably improve the display logic there.

Right now, the content is set to "Loading preview" until we receive a valid response from the server, at which point, it's set to the content we receive in the response. If the response is not valid, it does nothing an gets stuck at "Loading preview"

[begedin]

This issue will likely be fixed API-side. When code-corps/code-corps-api#219 is merged, we should revisit to check if there's still a problem.

[joshsmith]

@begedin can you check status of this?

[joshsmith]

@begedin ping.

[begedin]

I made the checks here, and while this specific issue (with a validation error) is gone, It's till not bulletproof.

If we click "new post", when just go immediately to preview, a request will be sent to the API with markdown_preview set to null, causing the API to fail with

If we focus the tab first, then "" will be sent as the markdown_value, so everything will work as expected. I think we should sanitize markdown_preview on the API side, so this one can be closed in favor of code-corps/code-corps-api#256

[joshsmith]

Okay, closing in favor of that issue.