console.log in template literals are also modifie by server logging
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- react, typescript
- Domain
- devtools
Research direction
Start with the linked CodeSandbox example, especially app/welcome/welcome.tsx lines 14–15, and trace how server logging processes console.log text inside rendered child content. Done means code snippets containing console.* no longer receive server-log modifications while genuine application logs continue to be enhanced; the issue does not name a test file.
Written by the indexing model from the issue text.
Description
It took me a while to understand why some code snippets in my apps with console logs started displaying some weird console.log output.
RRD seems to pick any console.log while enhancing logs, so any code snippets with console.* inside as well
Here an example
I am not sure of a simple way to differentiate console.log in the code from console.log rendered in a child.
- Dominant language
- TypeScript
- Stars
- 975
- Forks
- 55
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing 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.
More from code-forge-io/react-router-devtools
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
code-forge-io/react-router-devtools#247 · 12 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
code-forge-io/react-router-devtools#243 · 1 comment ·
All issues in code-forge-io/react-router-devtools
Similar issues
-
bug(core): JsonOutputKeyToolsParser ignores returnId: truePossibly taken A pull request linked to this issue is open or already merged. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
langchain-ai/langchainjs#12239 ·
Maintainers usually reply within 1 day
-
Board view: the Monitoring column is always empty because compact issue rows drop displayStatusOpen
Difficulty 1/5 Under an hour Newbie friendliness 88/100
paperclipai/paperclip#21837 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
code-yeongyu/senpi#6813 ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 93/100
lingdojo/kana-dojo#34169 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100