Strange typing for RegisterOptions['deps']

[timur-svoboda]

Here is the current typing (v7.43.5) for RegisterOptions:

export type RegisterOptions<TFieldValues extends FieldValues = FieldValues, TFieldName extends FieldPath<TFieldValues> = FieldPath<TFieldValues>> = Partial<{
    required: Message | ValidationRule<boolean>;
    min: ValidationRule<number | string>;
    max: ValidationRule<number | string>;
    maxLength: ValidationRule<number>;
    minLength: ValidationRule<number>;
    validate: Validate<FieldPathValue<TFieldValues, TFieldName>, TFieldValues> | Record<string, Validate<FieldPathValue<TFieldValues, TFieldName>, TFieldValues>>;
    value: FieldPathValue<TFieldValues, TFieldName>;
    setValueAs: (value: any) => any;
    shouldUnregister?: boolean;
    onChange?: (event: any) => void;
    onBlur?: (event: any) => void;
    disabled: boolean;
    deps: InternalFieldName | InternalFieldName[];
}> & ({
    pattern?: ValidationRule<RegExp>;
    valueAsNumber?: false;
    valueAsDate?: false;
} | {
    pattern?: undefined;
    valueAsNumber?: false;
    valueAsDate?: true;
} | {
    pattern?: undefined;
    valueAsNumber?: true;
    valueAsDate?: false;
});

Pay attention to the deps prop. This prop is responsible for creating dependencies between fields to trigger validation when dependencies change. That prop has the following type:

deps: InternalFieldName | InternalFieldName[];

I find this strange, because it doesn't provide useful typing. Why not to use more specific typing to improve developer experience? Something similar to this:

deps: FieldPath<TFieldValues> | FieldPath<TFieldValues>[]

Is there any reason for such typing?