App: [Bug] List of all the compose box related bugs that we need to get fixed soon
Coming from https://expensify.slack.com/archives/C01SKUP7QR0/p1666245169556899
I have categorized the issues based on the type/cause of the issue. Feel free to add more info/issues or update things to make it more clear and help us track them better.
Focus and cursor-related issue
- [Looking for proposals] #11093
Composer issue during transition
- [PR review in progress] #11471
- [Hold to Deprecate sequence number] #11293
- [Proposal review in progress] #8592
Emoji related issues
Offline related issue
- [Looking for proposal] #11265
Miscellaneous
- [Looking for proposals] #11921
Problem
Recently we have been seeing a lot of bugs related to compose box where some of them quite serious ones like Message deletes as you type, and message content staying in composer box even after the message was sent. Since it is one of the most important components of a chat app polishing it perfectly should be our end goal. Some of the issues that have popped up recently are regression that went unnoticed during tests so having a bird’s eye view will keep things neat and in control.
Goal
- Look into the list before you create a new issue to make sure there is no duplicates issue in the picture.
- While testing a PR related to compose box make sure you are not introducing any of the existing/completed bugs that are listed.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 1
- Comments: 16 (10 by maintainers)
👋 Hey-o! What are we accomplishing with this tracking issue? It seems undefined currently, so I’m not quite sure I understand its purpose. Looking at the solution (“goals”) stated in the OP:
This is the expectation across the board, to check the repo for duplicate issues.
How does anyone know to do this? Equally, you shouldn’t have to x-ref a tracking issue to avoid introducing new bugs in the code. That should be done through bettering documentation, the PR checklist etc.
We have other tracking issues that are actively working on a “wider” refactor or revisit to a flow/implementation to clean-up a bunch of bugs that have spawned from it. It doesn’t seem like we’re doing that here in this case.
Yeah I think that’s best for now.
Okay cool, so this seems like an actionable step if we think this is under tested. In which case, this issue should be updated to focus on that goal of identifying and writing missing tests.
For reference, here is the
compose boxsection of the Test Cases that exists in TestRail right now.Hi @jason, looking into other tracking issues it makes sense to just track the issues there either need help or are actively being handled by contributors. I will update the OP with the changes. Thanks