Tom Dracz

> @tomdracz Is there anything else we need to change for React 18 that I've missed? Think that covers it! > @tomdracz And to fix point 1, do you know...

> It's actually only used with Turbo, we really need integration tests for it. Added #1468. > > @tomdracz Actually, do you know if it _should_ be called on non-Turbo...

Caused by Devise authenticable module having custom inspect method: https://github.com/plataformatec/devise/blob/a0232cf76338927433f76e103fdfe8b66f93fe8a/lib/devise/models/authenticatable.rb#L119-L124 PP then tries its best to do something, but hasn't got line breaks or anything, as per https://github.com/ruby/ruby/blob/trunk/lib/pp.rb#L295-L321 Solution is...

Having the same issue here, looks like with native testing mode of Test Explorer there's some weirdness with running all tests. Disabling with `"testExplorer.useNativeTesting": false` makes the issue go away

For me, this one was solved by install/update of `@types/react` package. I had it at 16.9.5 and 16.9.35 silenced the warnings. Might possibly also fix #301

FWIW I've been playing around fixing some Shadow DOM issue using https://github.com/yuki24/capybara-shadowdom It still didn't play ball with likes of clicks not working because of some overlapping element issues. `let...

We've implemented some re-request scripting to run a dependant request using `bru.runRequest` but it seems like the dependencies cannot cross collection boundaries. In our case we had collection A and...

> does it mean you're assuming primitive type are nullable by default in your use cases? Not quite. It's around any attribute. Consider schema entity like: ``` Rfq: type: "object"...