Patrik Affentranger

Awesome @nikolayg, thanks for this :) @mattphillips would be awesome to get this merged, please :)

Found this article really helpful: https://www.freecodecamp.org/news/a-new-approach-to-mocking-graphql-data-1ef49de3d491/ Using both the [MockedProvider](https://www.apollographql.com/docs/react/development-testing/testing/#mockedprovider) for mock data and custom Loading and Error providers for those states is quite nice.

I had a similar problem, where tabbing through form fields on desktop or using the `` arrows on iOS would cause the slides/layout to break. I was able to solve...

Do you want me to log a new issue @alvarotrigo ? :)

I've spent some time experimenting with this and found the most consistent behaviour to be using the following config: ```tsx useDropzone({ accept: { '': ['.jpeg', '.png'] }, useFsAccessApi: false, })...

I noticed the following warnings in the console now that I started using empty mime-types despite it actually working as desired... ```tsx useDropzone({ accept: { '': ['.png', '.jpeg'], } })...

I agree with @pachuka, it would've been nice to be able to opt-out of this behaviour. Our use-case is the same and the vast majority of SVGs used in our...

@vkemeter you have the power to contribute to the code base by fixing whatever you think is broken and submit a pull request for it :)

I feel as though `@charset 'utf-8';` at the top of the file would've fixed your issue, too?

The error happens when trying to set the `sitecoreContext` to `context.context` on the wrapped component https://github.com/Sitecore/jss/blob/dev/packages/sitecore-jss-react/src/enhancers/withSitecoreContext.tsx#L35 We also noticed that this only seemed to be an issue on SSR pages...