You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the incident description just throws the entered sanitized text between a set of <p></p>. For some flexibility it would be nice to maybe allow markdown for that field, so some formatting can be applied. Alternatively we could add different sections to the table, but I think there is a chance that people from different cities want different fields displayed, so markdown would allow us to relatively easily set that up in an import script, or add some structure to a longer description. We would have to make sure to not allow injection of arbitrary html scripts however.
A different, somewhat lower tech solution could be to just allow a certain subset of features (maybe just headers), or to make sure that line breaks in the provided text are shown as line breaks in the result
The text was updated successfully, but these errors were encountered:
Currently the incident description just throws the entered sanitized text between a set of
<p></p>
. For some flexibility it would be nice to maybe allow markdown for that field, so some formatting can be applied. Alternatively we could add different sections to the table, but I think there is a chance that people from different cities want different fields displayed, so markdown would allow us to relatively easily set that up in an import script, or add some structure to a longer description. We would have to make sure to not allow injection of arbitrary html scripts however.A different, somewhat lower tech solution could be to just allow a certain subset of features (maybe just headers), or to make sure that line breaks in the provided text are shown as line breaks in the result
The text was updated successfully, but these errors were encountered: