INeedJobToStartWork / INeedJobToStartWork/Ghost-Ink
🐞[BUG] - CLEAR_OR_REPLACE_SELECTION is not working like should
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
### Issue Description
CLEAR_OR_REPLACE_SELECTION is not working like should, has issue and conflict with `ADD_CHAR_RIGHT` from `useWriting`
### INEEDJ Version
newest
### Tested on Latest Version
- [x] Yes
### Reproduction
_No response_
### Process to Reproduce bug
_No response_
### Photo/Images Showing Bug
_No response_
### Logs
_No response_
### What we got - What we expected
_No response_
### Additional Context
_No response_
### What did you try to fix it?
_No response_
### How did you solve it?
_No response_
### How problem can be solved?
_No response_
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating CLEAR_OR_REPLACE_SELECTION and ADD_CHAR_RIGHT in the useWriting entry point. Reproduce the selection interaction described in the issue, then trace where the two actions conflict. Done means the intended CLEAR_OR_REPLACE_SELECTION behavior is established and the ADD_CHAR_RIGHT conflict no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100