Igor Wessel

I realized it's not a good idea to do this due to the .not operators.

> I started looking at this too. I used this script to do the bulk rename. You might find it useful. > > ```shell > #!/usr/bin/env bash > set -o...

I'm thinking of putting validations in runtime for the ***actual*** one that is received via expect. What do you think about it? e.g (I took it from jest repo): ```ts...

> Sorry for the late reply on this. Since, as you say, Jest's built-in [matchers](https://github.com/facebook/jest/blob/main/packages/expect/src/matchers.ts) do runtime checks, so it seems reasonable to do it here as well. No problem....

@keeganwitt @mattphillips I needed an opinion before proceeding with the other files, I thought of doing the validations as follows. And I'll probably only add the validations to matchers that...

Regarding this function I didn't really like the fact that I'm passing the value but currently I'm not doing anything with him. I only use it to get to be...

I managed to make the manual import work with the correct types. I separated the matcher declaration as above and added the declarations for the typescript to start understanding exports...

Another problem that I forgot to mention is that if you separate the types every time you add a new matcher, you would have to update the file ***src/matchers/index.d.ts***. We...

> I have a minimal setup with no Jest config file and only one file of tests, and—going off the link from the comment above—I was able to get it...

> I prefer @xstyled/styled-components/native over @xstyled/styled-components-native due to all the duplication. We can maybe install as a dependency in ```@xstyled/styled-components``` and export all this guy > Maybe there is a...