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
Now there are so many traces, the output provided by traces() is confusing. I think it would be an improvement to group traces into related areas.
traces()
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered:
a little standardisation on trace names would be good too (e.g. spaces vs underscores, capitals, ...)
Sorry, something went wrong.
Yes, that's definitely true.
Some work in this direction appeared in 91d6676
No branches or pull requests
Now there are so many traces, the output provided by
traces()
is confusing. I think it would be an improvement to group traces into related areas.Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: