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
Is your feature request related to a problem? Please describe.
Long package/function names are impossible to read on small nodes
Describe the solution you'd like
We should provide a way to truncate the full function name either by:
automatically displaying only the function name on small nodes (like https://gotraceui.dev/ does), or
by providing buttons on the UI to remove/add parts of the full name (truncate until the next slash, for instance)
(github.com/grafana/quickpizza/pkg/http.(*Server).ServeHTTP becomes grafana/quickpizza/pkg/http.(*Server).ServeHTTP, then quickpizza/pkg/http.(*Server).ServeHTTP, etc.)
Alternatives considered
Describe alternatives you've considered
from @Rperry2174
Instead of a simple truncation, we could implement an incremental name expansion feature similar to the "decimal" button in Google Sheets. This approach allows users to progressively reveal more context in function names, based on logical segments (e.g., slashes / or dots .).
Example Table: Incremental Function Name Expansion
This method provides users with control over how much of the function name is displayed, helping them see relevant context without overwhelming them with the full string immediately. It avoids arbitrary truncation and adapts better to different naming conventions across languages.
This issue has been automatically marked as stale because it has not had activity in the last 90 days. It will be closed in 2 weeks if no further activity occurs.
Feature description
Is your feature request related to a problem? Please describe.
Long package/function names are impossible to read on small nodes
Describe the solution you'd like
We should provide a way to truncate the full function name either by:
(
github.com/grafana/quickpizza/pkg/http.(*Server).ServeHTTP
becomesgrafana/quickpizza/pkg/http.(*Server).ServeHTTP
, thenquickpizza/pkg/http.(*Server).ServeHTTP
, etc.)Alternatives considered
Describe alternatives you've considered
from @Rperry2174
Instead of a simple truncation, we could implement an incremental name expansion feature similar to the "decimal" button in Google Sheets. This approach allows users to progressively reveal more context in function names, based on logical segments (e.g., slashes
/
or dots.
).Example Table: Incremental Function Name Expansion
github.com/grafana/quickpizza/pkg/http.(*Server).ServeHTTP
ServeHTTP
http.(*Server).ServeHTTP
quickpizza/pkg/http.(*Server).ServeHTTP
github.com/grafana/quickpizza/pkg/http.(*Server).ServeHTTP
com.example.myapp.services.UserService.getUserById
getUserById
UserService.getUserById
services.UserService.getUserById
com.example.myapp.services.UserService.getUserById
my_project.module.submodule.ClassName.method_name
method_name
ClassName.method_name
submodule.ClassName.method_name
my_project.module.submodule.ClassName.method_name
Why This Approach?
This method provides users with control over how much of the function name is displayed, helping them see relevant context without overwhelming them with the full string immediately. It avoids arbitrary truncation and adapts better to different naming conventions across languages.
-
Additional context
Slack context: https://raintank-corp.slack.com/archives/C048VSWPZ4P/p1721936010915859?thread_ts=1721935610.960829&cid=C048VSWPZ4P
The text was updated successfully, but these errors were encountered: