-
-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(fromTraffic): match query parameters #46
Conversation
Add support to strictly match query parameters of a HAR file's request entry by matching the query string with the `queryString`-property of the entry.
@@ -56,7 +56,7 @@ | |||
"@types/compression": "^1.7.1", | |||
"@types/node": "18", | |||
"compression": "^1.7.4", | |||
"jsdom": "^22.1.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
jsdom has a bug in URLSearchParams.prototype.delete
. It ignores explicit value
argument when dealing with multiple key/value pairs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great! Thanks, @weyert 👏
I've added a few changes:
- Support for multi-value search parameters;
- Dropped jsdom in favor of happy-dom (fewer bugs);
- Added some test cases;
- Polished the implementation.
TILHappyDOM returns case-sensitive header names while neither the browser nor Node.js does that. Header names are lowercased per spec. |
Released: v0.2.0 🎉This has been released in v0.2.0! Make sure to always update to the latest version ( Predictable release automation by @ossjs/release. |
Add support to strictly match query parameters of a HAR file's request entry by matching the query string with the
queryString
-property of the entry.fixes #45