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

fix/4068 batchInsert correct definitions #4131

Merged

Conversation

maximelkin
Copy link
Collaborator

Closes #4068

@kibertoad
Copy link
Collaborator

@maximelkin One of the TSD tests are failing, try running npm run lint:types (or just tsd) locally.


// assert any bad column from returning list gives error
// tsd gives error on this, lol
/*expectError(
Copy link
Collaborator

Choose a reason for hiding this comment

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

Do you think that tsd is wrong here? If there is an easy self-contained repro possible, perhaps an issue at https://github.com/SamVerschueren/tsd/issues could be opened?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Copy link
Collaborator

Choose a reason for hiding this comment

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

Thank you. Can you add the reference to that bug report next to the commented out code?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I will try to fix it fast in tsd

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

does tsd have any caches? I cant reproduce it anymore on extracted example

Copy link
Collaborator

Choose a reason for hiding this comment

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

Not tsd per se, but TypeScript definitely has some caches, so that might have been a factor.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Oh, i copied stacktrace from wrong place

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Error pops up because this expression give 2 errors, but expectError allows only one

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

alternative fix is expectError(expectError())

@maximelkin
Copy link
Collaborator Author

tsc typecheck failing pipeline, I will try to fix (probably disable typecheck on them idk)

@maximelkin
Copy link
Collaborator Author

#4138 @kibertoad

@maximelkin maximelkin force-pushed the fix/4068_correct_batchInsert_definitions branch from abea2a8 to c98699c Compare November 25, 2020 23:22
@kibertoad kibertoad merged commit 619f286 into knex:master Nov 27, 2020
@kibertoad
Copy link
Collaborator

Thanks!

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.

batchInsert fix return type in typings
2 participants