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
When I was using typescript with ant-motion, I found moment set to null is unacceptable. since the typing as follow:
moment
null
export interface IProps<T> extends Omit<React.HTMLAttributes<T>, 'onChange'> { animation?: IAnimObject | IAnimObject[]; paused?: boolean; reverse?: boolean; reverseDelay?: number; repeat?: number; yoyo?: boolean; onChange?: (e: IChangeProps) => void; moment?: number; // should be number or undefined. attr?: IAttrType, resetStyle?: boolean, component?: string | React.ReactNode; componentProps?: {}; }
In vanilla Javascript, it is OK to set as null. but not in typescript, maybe you could change the API doc, to avoid misunderstanding.
https://motion.ant.design/api/tween-one-cn#API
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When I was using typescript with ant-motion, I found
moment
set tonull
is unacceptable.since the typing as follow:
In vanilla Javascript, it is OK to set as
null
. but not in typescript, maybe you could change the API doc, to avoid misunderstanding.https://motion.ant.design/api/tween-one-cn#API
The text was updated successfully, but these errors were encountered: