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

fix(react): prevent generating empty props since setting strict in tsconfig is not compatible with it #26428

Merged
merged 1 commit into from
Jun 6, 2024

Conversation

jaysoo
Copy link
Member

@jaysoo jaysoo commented Jun 6, 2024

This PR updates the React components so that interface for props is not generated. Some components don't have them, and users know how to add them if needed. This makes the generated component pass type checking if strict: true is used in tsconfig.

Current Behavior

Expected Behavior

Related Issue(s)

Fixes #

@jaysoo jaysoo requested review from a team as code owners June 6, 2024 17:55
@jaysoo jaysoo requested review from xiongemi and leosvelperez June 6, 2024 17:55
Copy link

vercel bot commented Jun 6, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment
Name Status Preview Updated (UTC)
nx-dev ⬜️ Ignored (Inspect) Visit Preview Jun 6, 2024 8:14pm

@jaysoo jaysoo force-pushed the fix/react-strict-checks branch from 8aa335d to fcddd07 Compare June 6, 2024 20:12
@jaysoo jaysoo enabled auto-merge (squash) June 6, 2024 20:12
@jaysoo jaysoo merged commit ec5461f into master Jun 6, 2024
6 checks passed
@jaysoo jaysoo deleted the fix/react-strict-checks branch June 6, 2024 20:40
Copy link

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 14, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants