AOSSIE-Org / AOSSIE-Org/DebateAI
[FEATURE]: Debate statements displayed as long paragraphs instead of bullet points in UI
- Dominant language
- TypeScript
- Stars
- 84
- Forks
- 198
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 30
Description
### Feature and its Use Cases
**Description**
Currently, the debate arguments generated by the bot are displayed as long paragraphs in the UI, even though the response content logically represents separate argument points.
Displaying these arguments in paragraph format makes the debate harder to read and follow, especially when multiple arguments are presented in a single response.
**Problem**
Bot responses often contain multiple arguments in a single message.
These arguments appear in the UI as continuous paragraphs.
This reduces readability and clarity during debates.
Example (current behavior):
> AI could automate many tasks and improve efficiency. It could reduce human error and optimize systems. It may also create new opportunities.
**Expected Behavior**
Debate responses should be rendered as bullet points so that each argument is clearly separated.
Example (expected behavior):
- AI could automate many tasks and improve efficiency
- It could reduce human error and optimize systems
- It may also create new opportunities
### Additional Context
**Actual Behaviour**
**Expected Behaviour**
### Code of Conduct
- [x] I have joined the [Discord server](https://discord.gg/hjUhu33uAn) and will post updates there
- [x] I have searched existing issues to avoid duplicates
Contributor guide
No contributing guide indexed for this repository
Research direction
No file or test is named. Start at the frontend entry point that renders bot debate responses and trace how a response is split or formatted for display. Compare the output with the issue’s expected bullet-point example and add or update coverage if the project has UI tests; done means separate arguments render as readable bullet points.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100