Plugin Confilct: Command Line and Line Numbers
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13k
- Forks
- 1.4k
- Avg merge
- 15h 36m
- Merged PRs (30d)
- 3
Description
Information:
- Prism version: [e.g. 1.14, latest from the download page, etc.] latest
- Plugins: [a list of plugins you are using or 'none'] Command Line and Line Numbers
- Environment: [e.g. Browser, Node, Webpack] Node
Description
A clear and concise description of what the bug is and how to reproduce it.
If applicable, add screenshots to help explain your problem.
Plugin Confilct: Command Line and Line Numbers
Example
An example which reproduces the bug. This can be a link to a website, a JSFiddle, an attached example project, etc.
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
Start with Prism's basic usage section and reproduce the reported conflict between the Command Line and Line Numbers plugins in the stated Node environment. Use the attached screenshot and the download-page version as reference, then document a minimal reproduction and verify that both plugins work together without the reported conflict.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100