[all components] Console Warnings as actual warnings

Open
#38,278 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, react
Domain
frontend

Research direction

Start by locating how console warnings are emitted across the components. Determine whether a consistent way to distinguish warnings from errors can be applied globally without hiding actual errors. Done means warnings appear as proper console warnings, with the behavior verified across the affected components.

Written by the indexing model from the issue text.

Description

scope: all components
Summary 💡

Warnings in MUI show as errors in the console.
It is a problem when you have some large warnings and you cannot find actual errors because of them.

I know warnings are important and they shouldn't be ignored, but there should be a way to make them show as proper warnings and not errors. Maybe some kind of global flag you change like showWarningsAsErros that is true by default.

Examples 🌈

mui-warning

Dominant language
JavaScript
Stars
99.1k
Forks
32.5k
Avg merge
2d 17h
Merged PRs (30d)
106

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mui/material-ui

All issues in mui/material-ui

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.