We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auto-generated names litter the console and interfere with readability. I propose to make the output of the scope name optional and hidden by default.
The text was updated successfully, but these errors were encountered:
Hmm, maybe it may work like this?
I think, it is still better to somehow distinguish non-scope and in-scope updates 🤔
debug({ scopeFullName: false }, ...units) // [store] $name 1 // [store] (in-scope) $name 2
Sorry, something went wrong.
Or maybe some smaller auto-generated name would do the trick?
E.g. shorter form:
// [store] (scope: unknown_1) $name 42
or just a number of scope:
// [store] (scope: 1) $name 42
In applications with ssr, you should't have logic outside the scope. And in next js, the scope is also recreated regularly.
A some smaller auto-generated name may improve the situation, but not solve it
No branches or pull requests
Auto-generated names litter the console and interfere with readability.
I propose to make the output of the scope name optional and hidden by default.
The text was updated successfully, but these errors were encountered: