We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The object type in the line
final-form/src/index.d.ts
Line 133 in 0d7aecb
Breaks the rule https://github.com/typescript-eslint/typescript-eslint/blob/v4.22.0/packages/eslint-plugin/docs/rules/ban-types.md
This error occurs outside the library code when implementing the field-level-validation example in TypeScript:
const composeValidators = (...validators: FieldValidator<string>[]) => (value: string, allValues: object) => validators.reduce((error, validator) => error || validator(value, allValues), undefined);
I think this can be fixed with
-type FieldValidator<FieldValue> = ( +type FieldValidator<FieldValue, FormValues> = ( value: FieldValue, - allValues: object, + allValues: FormValues, meta?: FieldState<FieldValue> ) => any | Promise<any> -type GetFieldValidator<FieldValue> = () => - | FieldValidator<FieldValue> +type GetFieldValidator<FieldValue, FormValues> = () => + | FieldValidator<FieldValue, FormValues> | undefined
and a few propagating changes including react-final-form.
What are your thoughts on this?
The text was updated successfully, but these errors were encountered:
object
FieldValidator
No branches or pull requests
What is the current behavior?
The object type in the line
final-form/src/index.d.ts
Line 133 in 0d7aecb
Breaks the rule
https://github.com/typescript-eslint/typescript-eslint/blob/v4.22.0/packages/eslint-plugin/docs/rules/ban-types.md
This error occurs outside the library code when implementing the field-level-validation example in TypeScript:
I think this can be fixed with
and a few propagating changes including react-final-form.
What are your thoughts on this?
The text was updated successfully, but these errors were encountered: