Skip to content
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

Consider formatted output for comments, e.g. could use Markdown #1162

Open
13 tasks
srabraham opened this issue Apr 5, 2024 · 4 comments
Open
13 tasks

Consider formatted output for comments, e.g. could use Markdown #1162

srabraham opened this issue Apr 5, 2024 · 4 comments
Assignees

Comments

@srabraham
Copy link
Member

srabraham commented Apr 5, 2024

The comments in IMS could be made to allow simple Markdown formatting, such that it's displayed that way after comments are appended. It especially seems like it'd be useful to support ordered lists (1. 2. 3.) or unordered lists (* * *).

Goals

  • Find an appropriate jQuery compatible field editor library / component which ideally outputs MarkDown
  • Editor should be use-able by non-devs who don't know what MarkDown is.
  • Disable any features that aren't compatible or aren't reasonable for our use case (images/video until we add that feature)
  • We may need a separate MarkDown view library for display.
  • Decide how to handle any summary versions of those fields.
  • Implement Editor in report creation screens
  • Implement Editor in report edit screens
  • Implement Editor in incident creation screens
  • Implement Editor in incident edit screens
  • Implement Viewer in report detail screens
  • Implement Viewer in incident detail screens
  • Implement Viewer in report list screens (if needed)
  • Implement Viewer in incident list screens (if needed)

Related Issues

@srabraham
Copy link
Member Author

Wood Ape mentioned something like this in our call tonight

@srabraham srabraham changed the title Consider formatted output for comments, e.g. Markdown Consider formatted output for comments, e.g. could use Markdown Apr 5, 2024
@chaoticbear
Copy link
Contributor

I think this is mostly a front-end task, though it's possible we may need to modify the model here a bit to handle formatted fields (or flag them as formatted)

So I think we'll want to update the legacy FE in this repo and make any model changes needed, in addition to the React FE. I've created an issue for the React FE and added it to the description.

@srabraham
Copy link
Member Author

This idea is in early stages, and I'd love to hear Tool's thoughts too

@chaoticbear
Copy link
Contributor

I added a rough outline for notation purposes of what we need to figure out / do. Obviously it can change as we go.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants