feat(network): show newest requests at the top of the Network tab - #449
Open
dimashbk wants to merge 1 commit into
Open
feat(network): show newest requests at the top of the Network tab#449dimashbk wants to merge 1 commit into
dimashbk wants to merge 1 commit into
Conversation
With oldest-first ordering fresh requests land at the bottom of a long list and are easy to miss; flip the display order and drop the scroll-to-bottom behavior that went with it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The Network tab lists requests oldest-first, so on a busy app the request you just made lands at the bottom of a long list — the debugging workflow becomes "open tab, scroll to the end, repeat". This flips the list to newest-first (like most network consoles) and removes the scroll-to-bottom behavior that compensated for the old order.
Happy to gate this behind a setting (e.g.
DebugSwift.Network.shared.newestFirst, defaulting to current behavior) if you prefer not to change the default — let me know.Type of change
Test plan
Manual test steps
Screenshots / recordings (if applicable)
Behavior change is ordering-only; list rendering unchanged.
Checklist