This repository has been archived by the owner on Aug 13, 2018. It is now read-only.
Query String parsing #62
Merged
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
…ature/query-string-parsing
|
Ah, this has been sitting here for quite a while, merging in. Thanks for great work as usual! Honza |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What
This PR adds a new feature to websocket-monitor, making it possible to display a query string as a
TreeView. See the screenshot below for an example.Why
Because I was bored 😄
No really, at work we use query strings at work to configure our serverside components to send a custom response. As I have mentioned before, these are strings in the form of
subscribe?.... This feature will make it a lot easier to read these strings. It also urldecodes the values of the fields for convenience.