Skip to content

Conversation

@DropsOfSerenity
Copy link
Contributor

The previous code had the chance of removing the profiler-totals when the max traces to show limit is hit, due to the profiler-results with profiler-totals row being the first row.

This would result on the rack mini profiler being unclickable and completely hidden when there are more than max traces to show. Breaking it entirely.

I think theres a bigger discussion about if we can support a way to see all traces, or paginate them in some way. But I think that's for another PR/discussion.

The previous code had the chance of removing the profiler-totals when
the max traces to show limit is hit, due to the profiler-results with
profiler-totals row being the first row.
@DropsOfSerenity DropsOfSerenity changed the title Profiler totals rows are not part of results. Profiler totals row should not be part of results. Jan 30, 2025
@coalest
Copy link
Collaborator

coalest commented Feb 10, 2025

Tested this out and it looks good to me!

I set the max_traces_to_show to be 5 so that the bug would be more apparent.

Before: (badge disappears after fifth trace added)

Screencast.from.2025-02-10.15-44-36.webm

After: (badge stays on the page)

Screencast.from.2025-02-10.15-45-57.webm

@nateberkopec
Copy link
Collaborator

Thanks! Changelog entry please 🙏

@DropsOfSerenity
Copy link
Contributor Author

Thanks! Changelog entry please 🙏

@nateberkopec Great! Will add it this week.

@DropsOfSerenity
Copy link
Contributor Author

@nateberkopec Added a changelog entry

@nateberkopec nateberkopec merged commit 1b42966 into MiniProfiler:master Apr 13, 2025
3 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants