Skip to content
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

Continuation PR #1169: change content-type-parser to whatwg-mimetype #1177

Merged
merged 11 commits into from Jan 5, 2022

Conversation

tommyhtran
Copy link
Contributor

@tommyhtran tommyhtran commented Dec 26, 2021

I'm picking up where @lagden left off from #1169.

lagden and others added 7 commits October 4, 2021 13:58
…s of the old request module to Axios, improve documentation of several functions' arguments.
The upstream pull request 1169 failed linting with the following error:
ERROR: /home/runner/work/node-soap/node-soap/src/http.ts:9:1 - Import sources within a group must be alphabetized.
@jsdevel
Copy link
Collaborator

jsdevel commented Dec 27, 2021

@tommyhtran please check the build log and ensure it passes

…d to MIMEType.parse().

The MIMEType constructor method throws an Error object on failure, unlike the call to contentTypeParser() from the 'content-type-parser' package, which returned null on failure. To maintain backwards compatibility, use MIMEType.parse(), which returns null on failure.
@tommyhtran
Copy link
Contributor Author

Please accept #1178 before accepting this pull request because whatwg-mimetype v3.0.0 specifies Node >=12 in its package.json.
https://github.com/jsdom/whatwg-mimetype/blob/v3.0.0/package.json#L33-L35

@tommyhtran
Copy link
Contributor Author

@jsdevel Is there anything holding up these PRs?

@jsdevel
Copy link
Collaborator

jsdevel commented Jan 3, 2022

@tommyhtran i merged #1178. please update this branch accordingly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants