Fix an issue with negative request/response sizes displayed. #234
Conversation
This file contains 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
|
Hi again @MiSikora. |
|
Oh, ok. I agree it makes sense to show |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
📷 Screenshots
Show us what you've changed, we love images.
📄 Context
Why did you change something? Is there an issue to link here? Or an extarnal link?
I introduced a bug with one of the previous PRs.
📝 Changes
Which code did you change? How?
I modified the response/request length on the UI level to display at lest
0as a minimum value.Is there something breaking in the API? Any class or method signature changed?
No.
📝 How to test
Is there a special case to test your changes?
Run the sample app. Requests and responses should display
0 Binstead of-1 Bfor some of the responses.🔮 Next steps
Do we have to plan something else after the merge?
No.