-
-
Notifications
You must be signed in to change notification settings - Fork 347
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
Allow markdown rendering to handle no-ops #139
Comments
thank you 👍 |
…fio-event#139 also add error handler on client-side
I decided to leave the server alone because it makes sense to fail when there is no text param. Do you think I should make the text parameter optional and return an empty string when it isn't provided? @cbellone |
Pressing the "Preview" button in the I added the default value for the |
Hi @bunsenmcdubbs, I would suggest the following:
how does it sound? |
Sounds good. I created PR #141 |
merged! thank you! |
When creating new events, the client sends off an errant request to the server to render markdown that isn't yet there (sends a request directly to
http://localhost:8080/admin/api/utils/render-commonmark
)This causes an error on the server because the endpoint expects an query parameter
text
.This should be a simple fix on both client and server side. I can take care of it in a PR.
The text was updated successfully, but these errors were encountered: