Typescript definitions for TableCell
See original GitHub issue@material-ui/core/TableCell/TableCell.d.ts (13,64): Type '"align"' does not satisfy the constraint '"color" | "hidden" | "dir" | "slot" | "style" | "title" | "children" | "defaultChecked" | "defaultValue" | "suppressContentEditableWarning" | "suppressHydrationWarning" | "accessKey" | ... 240 more ... | "scope"'.
- This is not a v0.x issue.
- I have searched the issues of this repository and believe that this is not a duplicate.
Expected Behavior 🤔
Current Behavior 😯
Steps to Reproduce 🕹
Link:
Context 🔦
Your Environment 🌎
Tech | Version |
---|---|
Material-UI | v3.8.3 |
React | 16.4.14 |
Browser | Chrome |
TypeScript | 3.2.1 |
etc. |
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:11 (6 by maintainers)
Top Results From Across the Web
TableCell API - Material UI - MUI
API reference docs for the React TableCell component. Learn about the props, CSS, and other APIs of this exported module.
Read more >Property 'Cell' does not exist on type from @type/react-table in ...
It's easy to declare that the Cell only needs a value prop, but you have to state that explicitly. export const name =...
Read more >React MUI v5 Table Tutorial: TypeScript, Styling, and ...
This tutorial explores the subcomponents that compose a table, styling the table the MUI v5 way, TypeScript, and a few Table props.
Read more >TableCell Class (System.Web.UI.WebControls) | Microsoft Learn
The TableCell class allows you to control how the contents of the cell are displayed. The alignment of the contents in the cell...
Read more >HTML DOM Table cells Collection - W3Schools
Definition and Usage. The cells collection returns a collection of all <td> or <th> ... Change the content of the first table cell:...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
If it is possible try to pin all your
@types/*
packages. It would be IMO way better if no one would bundle their types since semver can’t be applied to type declarations because TS itself doesn’t follow semver and type declarations are usually behind their actual implementation which means even minor changes can cause breakage.However it’s way easier for us to maintain our types if we have full control over them. Moving them to the DefinitelyTyped monorepo would slow everything related to material-ui down. We try to not rely on new features in
@types/react
and usually breakage shouldn’t happen to often.I can’t really give you a satisfying answer to this issue. If this happens again just look at the
@types/*
versions we have inyarn.lock
and try to reconcile them with your types.You need to upgrade
@types/react
. If this is not possible you can addskipLibCheck: true
to your tsconfig. This might disable some type checks in your code base though so I would be careful. Upgrade@types/react
is recommend although it might cause other issues in your codebase.