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
Integration with typescript appears to be broken when using latest deps #3824
Comments
I'm seeing this also. I was able to update to as far as |
+1 |
Hey, @DarrienG, you are correct that our types for button are wrongly requiring We're changing these types even further soon (within 2 weeks, maybe this week!) as a part of our breaking change release, so hopefully this isn't a problem ever again. See this PR comment for details: #3622 (comment) |
I'm not entirely sure what it all means, but I appreciate the work being done to fix it and hopefully make it so it doesn't happen again. Thank you! |
Still seeing this issue occur when consuming the TextInput component in a downstream typescript project. |
If I remember correctly, I met this issue in components |
Confirming it is still not fixed on the latest release. My assumption is that the fix hasn't been made into an official release yet. Current latest version with the issue: |
Hey @DarrienG , I believe this should be fixed in our latest release, |
Confirming now it is fixed for some components, but not all. TextInput is one of the components still broken (but Button is now fine).
I updated the repo I was using to show the issue to It seems like some components got the update, but others didn't? I'm not certain all of the components that may or may not have been fixed, but |
Could this issue be updated when a release with the fix is pushed out? I check in every so often, and update every once in a while to see if it's fixed, but the latest release is still |
Hey @DarrienG , we're releasing Monday March 31 or Tuesday April 1. In the meantime you can try our prerelease package which is |
Describe the issue. What is the expected and unexpected behavior?
On the latest releases of patternfly/typescript, a number of components complain about the
css
property not being set.Error message in text:
I've done my due diligence here and tried to see if I can fix it myself and came across a number of related issues in other repos over the years.
The emotion repo is the most prominent that suffered from it a while ago: emotion-js/emotion#1249
With the fix being to add emotion types to compilerOptions: emotion-js/emotion#1249 (comment)
Adding:
Does not fix the issue.
I tried clearing my
yarn.lock
andnode_modules
and reinstalling and this did not fix either.Please provide the steps to reproduce. Feel free to link CodeSandbox or another tool.
I've included a repo I made a few minutes ago to demonstrate the error here.
https://gitlab.com/DarrienG/ts-patternfly-issue
Is this a bug or enhancement? If this issue is a bug, is this issue blocking you or is there a work-around?
The only workaround I can see is not upgrading my deps.
What is your product and what release version are you targeting?
I've included the info in the repo, but these are the patternfly versions that have the issue:
Using node 13.8.0, yarn v1.22.0 (all latest) on Ubuntu 19.10 (sorry not fedora).
Upgrading from
"@patternfly/react-core": "3.134.2
and"typescript": "3.7.2"
to"typescript": "3.7.4"
The text was updated successfully, but these errors were encountered: