cssinjs/jss

Verbose warning option?

Open

#1,485 opened on Mar 30, 2021

View on GitHub
 (5 comments) (0 reactions) (0 assignees)JavaScript (434 forks)batch import
bughelp wanted

Repository metrics

Stars
 (7,000 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Is your feature request related to a problem? Please describe.

I've been trying to debug some issues on my app to get it compatible with IE 11. In the process, I'm encountering a lot of warnings (only in IE) e.g. Warning [JSS] SyntaxError, Warning: [JSS] Rule is not linked. Missing sheet option "link: true".. I'm sure there's a valid reason for the warnings, but I'm at a loss as to where they are being triggered from or what the exact problems are, because the above warnings are the only information I have.

Describe the solution you'd like Ideally, I would like to at least have the option of seeing the full error stack when warnings are encountered by jss, so I can more easily identify what is causing the issues I'm running into. I'm not sure if such a behavior already exists, but from my investigation so far I have not found any.

Are you willing to implement it? Yes

Contributor guide

Research direction
Investigate how JSS currently emits warnings (likely in a utility function) and how options are passed (e.g., through jss.setup()). Review the issue comments for any maintainer feedback. Look at existing options like 'link: true' for precedent. The solution would likely involve adding a 'verbose' option to enable full stack traces, so examine the warning generation code in source files like src/utils/warning.js or similar.
Tech stack
javascript
Domain
frontend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
basic JavaScriptfamiliarity with JSS
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60