Christian Vuerings

More context is that there was an exception raised from an ESLint rule which ESLint showed but esprint not

Most likely root cause is that we're using a dynamic page route: `docs/pages/[...id].js` for the markdown pages

@AlbertCarreras @dangerismycat thank you for the feedback and list of issues you encountered. It was totally fine to disable them since they blocked the team. Couple of notes below of...

@AlbertCarreras @dangerismycat want to take another look at this diff? I updated the PR description with all the changes to make the playwright tests faster, less flaky & easier to...

@dangerismycat @AlbertCarreras heads up that I also added a section to the docs about how to update the visual snapshots for a specific test:  Are there any other processes...

@AlbertCarreras @dangerismycat What do you recommend as next steps for this PR? Please let me know if something is missing. It's totally fine if we would have to disable the...

@AlbertCarreras or @dangerismycat could either of you take a look? Would love to merge this asap to avoid further merge conflicts (e.g. `gap` changes)

@zifahm you are correct, the bug is caused by React 18 - PR #2104 Before React 18 we don't see the flash: https://deploy-preview-2103--gestalt.netlify.app/sheet#Preventing-close-on-outside-click After React 18 we do see the...

@Brianzchen We already have `include_warnings=true` in our config but it would still be great to have the error code enforcement as an ESLint rule as well since: * We can...

@kettanaito That does look promising. Would there be a way to beta test this out with `msw`? I did have to update the import in your example: ```diff - import...