Skip to content

Conversation

phillipperalez
Copy link
Contributor

Adding ability to check status codes and return proper errors to Looker

@phillipperalez phillipperalez requested a review from a team as a code owner April 5, 2024 19:34
Jonting416
Jonting416 previously approved these changes Apr 5, 2024
Copy link
Collaborator

@drstrangelooker drstrangelooker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Jonting416
Jonting416 previously approved these changes May 9, 2024
Copy link
Contributor

@Jonting416 Jonting416 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM but it looks like there are a lot of events that we are no longer supporting (not sure if they are in the new fetch library either) - eg: socket, abort, finish, etc.

@phillipperalez
Copy link
Contributor Author

From what I could tell node-fetch did not offer the same event granularity as the request library. You do not receive the same type of events and errors will be piped to the catch/reject rather than an event.

"@types/express": "^4.17.17",
"@types/jsforce": "^1.9.33",
"@types/node": "^18.11.11",
"@types/node-fetch": "^2.6.11",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR says it's replacing the request library. Can we remove the dependency?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants