@hp77-creator is attempting to deploy a commit to the KeepHQ Team on Vercel.

A member of the Team first needs to authorize it.

@talboren Please let me know if this is alright?

@hp77-creator Well done!
I've just checked out your branch and tested locally!
I used Incident chat to generate summary and all formatting was preserved in Incident summary.
Looks great 👍

However, as far as I see, there is some incompatibility with Summary form control in "Edit incident" modal. This is the screenshot:

That shouldn't have happened, I think it is not rendering it, let me look into it. Will update you. Thanks

@skynetigor
can you tell me how did you get this screen?
I clicked on Edit incidents and it showed something like this:

@skynetigor can you share the type of formatting that you have used in your incident, I will try to recreate it.

@skynetigor can you tell me how did you get this screen? I clicked on Edit incidents and it showed something like this:

You need to have AI enabled and try to generate Incident summary with AI producing formatted text. It then is displayed good on Incident, but when you try to edit the incident, in the rich text Summary editor the formatting is broken..
https://docs.keephq.dev/deployment/configuration#openapi

Understood, but I don't have any API_KEY, so I guess I can't test it that way, can you share the text, which you see in the Edit window, I can try with that manner

`Incident Title: Cloudwatch Incident

Summary of Alerts:

1. ServiceMemoryAlert: Service memory usage is critical in 'worker-service'.
2. ContainerMemoryHigh: Container in 'cache-service' using excessive memory.
3. EndpointFailures: Critical endpoint failure detected in 'order-system', Priority: P1.
4. HighCPUUsage: CPU utilization is above threshold in 'mailing-app'.
5. PodRecycled: Pod recycled due to resource constraints in 'main-app'.
6. APIErrorRate: API error rate above normal levels in 'payment-api', Priority: P1.
7. HighMemoryUsage: Memory utilization exceeded threshold in 'api-service'.
8. ServiceErrors: High error count in 'user-service', Priority: P1.
9. HighCPUUsageOnAPod: Pod CPU usage exceeds safe limits in 'producers'.

Severity of all incidents: Info
Priority varies from P1 to P3.`

This is the summary generated by OpenAI and broken in rich text editor.
The main issue I think is because it's markdown but rich text editor works with plain html..

Sorry, I'm struggling to put this markdown text here because GH interprets it 🥲
I'll find a way to attach it

If you can add it in a txt file and attach it, i guess that will work 🤔

incident summary.txt

@skynetigor yes you are right, so showing it in ReactQuill will need some more changes inside editor, just want to know was it working before? In the scope of original issue we wanted to get only format for summary, right? should I update ReactQuill component?

Hi @hp77-creator
I noticed that "whitespace-pre-wrap" makes summary with markdown look ugly. If I remove this class, it looks better.
Could you please check this?
With the class:

Without the class:

This is the summary I tested with:
incident summary.txt

Let's check this issue (if it's an issue) and merge it. Although not all cases covered, I think the main issue was solved here. Now "summary" on Incident is displayed well for both AI generated summary and for summary created using rich text editor in create/edit form.

But the issue with incorrect handling of markdown in rich-text editor is worth being an another issue.

Noted @skynetigor
It was giving merge conflict, so I simply added it to resolve the conflict, will remove whitespace-pre-wrap.

I agree that create/edit one could be another issue. I am willing to take up that.

@skynetigor I have removed it. Let me know on the further course of action.

@hp77-creator merging it, thank you for your contribution 🙏

🚂 Fantastic work @hp77-creator! Your very first PR to keep has been merged! 🎉🥳

You've just taken your first step into open-source, and we couldn't be happier to have you onboard. 🙌
If you're feeling adventurous, why not dive into another issue and keep contributing? The community would love to see more from you! 🚀

For any support, feel free to reach out on the community: https://slack.keephq.dev. Happy coding! 👩‍💻👨‍💻

@skynetigor thanks a lot for being so patient and helpful. I will pick up the other issue as well. Let me know when you create it. Also joining slack.