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
When using version > v2.13.0 some types definitions referencing @mui/x-date-pickers are wrongly using generics
Example:
Before v2.13.0 (Correct use of generics):
After v2.13.0 (Incorrect use of generics):
Looking at src/types.ts for v2 it looks fine. But the types generated in dist when building seems to be different and wrong
For v2.13.0 there are six places where types are wrong
But for v2.13.1 only 3 places
So it seems part of the issue has been solved between v2.13.0 and v2.13.1 somehow
I'm not able to use tools like dts-bundle-generator because of this problem and had to downgrade to 2.12.1
Minimal, Reproducible Example - (Optional, but Recommended)
Optional
Screenshots or Videos (Optional)
No response
Do you intend to try to help solve this bug with your own PR?
Maybe, I'll investigate and start debugging
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:
material-react-table version
v2.13.0
react & react-dom versions
v18.3.1
Describe the bug and the steps to reproduce it
When using version > v2.13.0 some types definitions referencing @mui/x-date-pickers are wrongly using generics
Example:
Looking at
src/types.ts
for v2 it looks fine. But the types generated indist
when building seems to be different and wrongFor v2.13.0 there are six places where types are wrong
But for v2.13.1 only 3 places
So it seems part of the issue has been solved between v2.13.0 and v2.13.1 somehow
I'm not able to use tools like
dts-bundle-generator
because of this problem and had to downgrade to2.12.1
Minimal, Reproducible Example - (Optional, but Recommended)
Optional
Screenshots or Videos (Optional)
No response
Do you intend to try to help solve this bug with your own PR?
Maybe, I'll investigate and start debugging
Terms
The text was updated successfully, but these errors were encountered: