cssinjs/jss

Verbose warning option?

Open

#1 485 ouverte le 30 mars 2021

Voir sur GitHub
 (5 commentaires) (0 réactions) (0 assignés)JavaScript (7 000 stars) (434 forks)batch import
bughelp wanted

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

Guide contributeur

Stack technique
javascript
Domaine
frontend
Type d'issue
feature
DifficultéDifficulté estimée pour un nouveau contributeur, de 1 pour un très petit changement à 5 pour un travail expert.
2
Temps estiméFourchette de temps approximative pour investiguer, implémenter, tester et préparer une pull request.
1-3 hours
Statut d'activitéDisponibilité apparente de l'issue : fraîche, active, ancienne, bloquée ou en attente d'un mainteneur.
stale
ClartéClarté avec laquelle l'issue explique le changement attendu, les critères d'acceptation et la prochaine étape.
mostly clear
Prérequis
basic JavaScriptfamiliarity with JSS
Accessibilité débutantScore de 1 à 100 estimant l'accessibilité de cette issue pour un premier contributeur.
60
Direction de recherche
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.