-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Update styled-components_v4.x.x.js #3609
Conversation
Wouldn't this break some tests? |
@goodmind, it looks like the second commit broke some tests but it might be worth checking if the tests are checking for the right think. As it is right now, if you have a component that uses |
@pascalduez I don't recall working on this libdef nor do I have recollection of using this library. I'm happy to help weigh in though! If you need that please direct me to something specific you'd like me to look at :) |
@LoganBarnett Oh sorry, I must have been confused with another library then. ;) |
The reason exact is used because of how spread in some inexact circumstances currently behaves (or "misbehaves"). There are some pretty cool and upcoming changes to how spreads will behave in Flow (Search for Once that is released (probably 0.111?), I think think that most of this will need quite a bit of reworking because it will start generating a lot of errors. So, for the time being, I would keep the typo commit, and drop the other two commits. Once the spread changes are live, we can revisit these libdefs. |
@omninonsense, that sounds good. I'll follow up once the spread semantics release is out! For now I'll drop the non-typo commits. |
LGTM! ❤️ |
I'm wondering about the build? Was it broken previously for this libdef @omninonsense ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
n/m, obviously the build was broken previously because this change couldn't have caused all those errors. Merging.
These changes remove the coercion of props to exact and properly uses the component's instance.
Would love to hear from the type maintainers if this is a welcome change and what I can do to help make the types better!