Add logging at INFO and DEV level
Open
Nobody has claimed this yet.
enhancement
good first issue
- Dominant language
- Lua
- Stars
- 22
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Functions within bidi.nvim should be provide information during execution for better debugging.
If someone's file gets corrupted, they should have a way to see what code was used on it.
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or entry points are named. Inspect the Lua functions in bidi.nvim and the Neovim execution paths they use, then determine how INFO and DEV logging should expose execution details and the code applied to a file. Done means corrupted-file investigations can retrieve that information.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100