Skip to content
New issue

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

Components requesting placeholder prop after the latest update #547

Closed
ishahbaz7 opened this issue Dec 25, 2023 · 3 comments
Closed

Components requesting placeholder prop after the latest update #547

ishahbaz7 opened this issue Dec 25, 2023 · 3 comments

Comments

@ishahbaz7
Copy link

After the latest update, several components in Material Tailwind are now requiring a placeholder prop. This was not the case in previous versions. Developers are prompted to provide a placeholder prop where it wasn't required before.

Steps to Reproduce:

Configure Material Tailwind with React Typescript
Utilize components that previously did not require a placeholder prop.
Observe the error or warning prompting for a placeholder prop.

Expected Behavior:
Components should function as intended without the need for a placeholder prop, as per previous versions.

Environment:

Material Tailwind version: 2.1.8
React version: 18

@don-esteban
Copy link

don-esteban commented Dec 25, 2023

Duplicate. See just a few issues below or a simple search: #528

npm install @types/[email protected]  // resolves all, but "Property 'crossOrigin' is missing" in Input.
npm install @types/[email protected]  // resolves all.

@ishahbaz7
Copy link
Author

I

Duplicate. See just a few issues below or a simple search: #528

npm install @types/[email protected]  // resolves all, but "Property 'crossOrigin' is missing" in Input.
npm install @types/[email protected]  // resolves all.

Thanks don-esteban. Its works.

@frankdavid-addae
Copy link

I was using @types/[email protected] and all of a sudden this issue came up again, and I have to downgrade to @types/[email protected].
Does that means this issues is still not resolved in latest versions of @types/react?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants