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 onError type #8667

Merged
merged 2 commits into from
Feb 20, 2023
Merged

Fix onError type #8667

merged 2 commits into from
Feb 20, 2023

Conversation

djhi
Copy link
Contributor

@djhi djhi commented Feb 20, 2023

Fix the onError type name to be Pascal cased like the others

export type onError = (error?: any, variables?: any, context?: any) => void;
export type OnError = onError;
Copy link
Member

Choose a reason for hiding this comment

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

I'd do it the other way around

export type OnError = (error?: any, variables?: any, context?: any) => void;;
// @deprecated - use OnError instead
export type onError = OnError

@fzaninotto
Copy link
Member

Can you please add a description?

@fzaninotto fzaninotto merged commit fba15c8 into master Feb 20, 2023
@fzaninotto fzaninotto deleted the fix-on-error-type branch February 20, 2023 10:16
@fzaninotto fzaninotto added this to the 4.8.1 milestone Feb 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
RFR Ready For Review TypeScript
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants