chrishawn
chrishawn
the main example above that i got this and still get this with is as you say `component-based queries with `
@MarcMcIntosh I don't see how this solves the problem at all if you do what you suggest in the example above you just get ```The prop `query` is marked as...
to stress, the `` from above works, it just throws a warning in the browser console ```Invalid prop `query` of type `object` supplied to `StaticQuery`, expected `string`.``` which should be...
This would be very useful, its less of a case of security and more of context, in multi-tenant case say a user has 3 different contexts (eg companies) with associated...
yes please review
yeah this isnt fixed in React 17.02 and notistack 2.0.8 using yarn at least
so the solution seems to be update to latest notistack 2.0.8 then do ``` "@types/react": "^18.0.26", "@types/react-dom": "^18.0.9", ``` even if you leave these at 17 ``` "react": "^17.0.2", "react-dom":...
The redirectURI has to start with "https://". Also make sure the redirectURI matches correctly with the page that opened the popup.