Asher Tuggle

We're seeing the same issue with cypress `9.6.1` on all of the `cypress/browser` images I've tried, which includes: - `cypress/browsers:node16.14.2-slim-chrome100-ff99-edge` - `cypress/browsers:node16.14.2-slim-chrome103-ff102` - `cypress/browsers:node16.13.2-chrome100-ff98` All of them are getting this...

Not sure why, but forcing the button to be re-mounted when changing `isOpen` seems to fix this issue. The easiest way to do this is setting a `key` prop on...

I looked into this as well a little bit ago. The `css` property is coming from Storybook; I tried compiling the library without Storybook, and the property was gone. I'm...

Adding `"src/stories"` to `exclude` in `tsconfig.json` would fix this issue. I don't know if it would negatively affect Storybook users, though, as I am not one.

I'm having an issue that's a bit more complex, but might be the same thing as this. Here's my reproduction repo: https://github.com/awesomeunleashed/ts-eslint-unsafe-bug-repro You can see the error in the README...

For what it's worth, using `fmt.Sprintf("%p")` would work for any `io.ReadSeeker`s that are already pointers, which is most likely the case in all real use cases. It wouldn't work well...

My main thoughts on that reasoning: 1. By using a panic, the importer is forcing the application using it to end on an error--likely fine for a simple command-line utility,...

Any chance this could be merged? It would be nice to not get an error if I forget there's automation and assign the project manually.