You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
mantineSearchTextInputProps is implied in the documentation to accept any props that exist for Mantine TextInput Docs, which should then include the data-autofocus part of focus-traps, for say, a Drawer. It is possible to just put it in anyway, but it does show up as an error.
Object literal may only specify known properties, and '"data-autofocus"' does not exist in type '(Omit<HTMLProps, "data" | "color" | "size" | "type" | "ref" | "label"> & { ref?: MutableRefObject<HTMLInputElement | null> | null | undefined; } & Partial<...>) | ((props: { ...; }) => Omit<...> & ... 1 more ... & Partial<...>)'.ts(2353)
index.d.ts(778, 5): The expected type comes from property 'mantineSearchTextInputProps' which is declared here on type 'MRT_TableOptions'
Minimal, Reproducible Example - (Optional, but Recommended)
mantineSearchTextInputProps:{
"data-autofocus" : true // shows as error
},
Screenshots or Videos (Optional)
Showing that ignoring the TSerror allows it to work.
Do you intend to try to help solve this bug with your own PR?
No, because I do not know how
Terms
I understand that if my bug cannot be reliably reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.
The text was updated successfully, but these errors were encountered:
mantine-react-table version
v1.3.4
react & react-dom versions
v18.2.0
Describe the bug and the steps to reproduce it
mantineSearchTextInputProps is implied in the documentation to accept any props that exist for Mantine TextInput Docs, which should then include the
data-autofocus
part of focus-traps, for say, a Drawer. It is possible to just put it in anyway, but it does show up as an error.Minimal, Reproducible Example - (Optional, but Recommended)
Screenshots or Videos (Optional)
Showing that ignoring the TSerror allows it to work.
![image](https://private-user-images.githubusercontent.com/123531217/305033951-f89e30fd-4ede-4f82-bf61-c3b6c14f59b9.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjUzMTMxOTksIm5iZiI6MTcyNTMxMjg5OSwicGF0aCI6Ii8xMjM1MzEyMTcvMzA1MDMzOTUxLWY4OWUzMGZkLTRlZGUtNGY4Mi1iZjYxLWMzYjZjMTRmNTliOS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwOTAyJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDkwMlQyMTM0NTlaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT00ZTUwM2E0YmFlYzExOWRjZGIyODcxYjBlMzFmZWQ0N2Y5OTljZjljZWI1NTU4NzI2NGI0MTA1ZDdhMTdjODE1JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.6ZeqZAYgMWTfk-EUpYnHntxWDXJDwSrMKCgCCfUlIqw)
Do you intend to try to help solve this bug with your own PR?
No, because I do not know how
Terms
The text was updated successfully, but these errors were encountered: