Eric Burel

After more investigation: - we are supposed to use "DataSources" in order to have the best performances for a request - DataSources must be recreated on a per request basis...

DataSources and connectors will be soon better supported. The "queriers" might reuse the "createContext" method to generate a valid graphql context internally. They probably should not use the "dataSources", but...

MSW also work for API:https://github.com/vercel/next.js/tree/canary/examples/with-msw

Done for Vulcan NPM, needs to be copied over Vulcan Next

https://github.com/vercel/next.js/discussions/13528

It's possible to alter the eslint config using an override: ``` { "files": [ /* test files for example */ ], "rules": { "react/react-in-jsx-scope": "off" } ```

Nowadays Next.js brings Jest support out of the box, we need to handle that

First version has been implemented by @Timi-Duban and visilble in the `/admin` page Next step: - figuring user creation (difficult because of the password) - fix currentUser handling in SmartForm...

Regarding private pages, it needs #49 and #71 needs to progress a bit until we get a proper architecture.

Regarding role management, we should probably keep Vulcan NPM as-is: simply include "guests" (or "anyone"), "members" and "admin" groups. Then, instead of trying to add groups into Vulcan, we could...