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
I'm fully aware of #5636 and don't want to reiterate again on this PITA discussion 馃槄
We have the problem in our project too and they are not bypassable atm. But we are aware and have some refactorings planned that will resolve it, but they will take some time. In the meantime, all these warnings are just so painfully annoying during the development process and we would like to disable those as you suggested here:
Remove the warning about dual usage (it will still occur, but we are basically just "hiding" it)
I would suggest I do a PR to polkadot-js/common introducing a check if an environment variable (e.g. POLKADOT_JS_DISABLE_PACKAGE_WARN) is set. And if yes, it doesn't print anything and skips the tests. This package is used within all other @polkadot/* packages, correct? So this change would be only necessary there.
The text was updated successfully, but these errors were encountered:
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.
Hey @jacogr,
I'm fully aware of #5636 and don't want to reiterate again on this PITA discussion 馃槄
We have the problem in our project too and they are not bypassable atm. But we are aware and have some refactorings planned that will resolve it, but they will take some time. In the meantime, all these warnings are just so painfully annoying during the development process and we would like to disable those as you suggested here:
I would suggest I do a PR to
polkadot-js/common
introducing a check if an environment variable (e.g.POLKADOT_JS_DISABLE_PACKAGE_WARN
) is set. And if yes, it doesn't print anything and skips the tests. This package is used within all other@polkadot/*
packages, correct? So this change would be only necessary there.The text was updated successfully, but these errors were encountered: