You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently use the warning module to emit warnings to developers when a code path they have encountered is deprecated. However, the warning module uses console.error under the hood, instead of console.warn, which has caused some issues that both our team and those in the React ecosystem has faced in terms of confusion.
Instead, it would be great if we could transition to console.warn usage instead of console.error, most likely through our own implementation of warning that we could then use in the codebase.
Make our custom warning function
Update where our code uses warning to use our custom warning function
Remove the warning dependency from carbon-components-react
The text was updated successfully, but these errors were encountered:
We currently use the
warning
module to emit warnings to developers when a code path they have encountered is deprecated. However, thewarning
module usesconsole.error
under the hood, instead ofconsole.warn
, which has caused some issues that both our team and those in the React ecosystem has faced in terms of confusion.Instead, it would be great if we could transition to
console.warn
usage instead ofconsole.error
, most likely through our own implementation of warning that we could then use in the codebase.warning
to use our customwarning
functionwarning
dependency fromcarbon-components-react
The text was updated successfully, but these errors were encountered: