This repository implements the react-query hooks and mutations for apps to consume the Graasp Apps API. It also provides a mock API server based on MirageJS for local development.
This apps-query-client package provides a mock API to mock any call an app might use to consume the Graasp API. It is based on MirageJS, which simulates the network requests themselves, and can thus remember remote state in memory. So the database is preserved as long as the app is not refreshed. This mock API is also particularly useful for continuous integration tests.
The following steps are designed to take into account Cypress
, our test framework. So the mock database can also receive data from the tests and apply them.
!WARNING: The mock API cannot fake uploading and downloading files!
- Install the
env-cmd
dependency. Create a new scriptstart:local
inpackage.json
:
"start:local": "env-cmd -f ./.env.development react-scripts start"
- Create
.env.development
which will contain the variables below. The app id you will choose doesn't have to be valid, but needs to exist.
REACT_APP_GRAASP_APP_ID=<your app id>
REACT_APP_GRAASP_APP_KEY=<your app key>
REACT_APP_ENABLE_MOCK_API=true
- Configure your query client in
src/config/queryClient.js
with the following code.
import {
configureQueryClient,
buildMockLocalContext,
buildMockParentWindow,
} from '@graasp/apps-query-client';
const values = configureQueryClient({
GRAASP_APP_KEY: process.env.REACT_APP_GRAASP_APP_KEY,
isStandalone: MOCK_API,
});
export values;
- Add the following content in
src/index.js
.mockApi
can take a defined context and/or database if necessary (see the Cypress section)
import { mockApi } from '@graasp/apps-query-client';
if (process.env.REACT_APP_ENABLE_MOCK_API === 'true') {
mockApi();
}
- Use the
withContext
and thewithToken
files in your app. It will handle the authentication and fetching the local context automatically for you. For example:
const AppWithContext = withToken(App, {
LoadingComponent: <Loader />,
useAuthToken: hooks.useAuthToken,
onError: () => {
showErrorToast('An error occured while requesting the token.');
},
});
const AppWithContextAndToken = withContext(AppWithContext, {
LoadingComponent: <Loader />,
useGetLocalContext: hooks.useGetLocalContext,
useAutoResize: hooks.useAutoResize,
onError: () => {
showErrorToast('An error occured while fetching the context.');
},
});
You can now start your app with the mock API installed. Don't forget to disable it when you build your app (set REACT_APP_ENABLE_MOCK_API
to false
).
The next steps will help you set up Cypress to work with MirageJS. There is an official tutorial from MirageJS. But in our case, we followed a different strategy.
- Update your content in
src/index.js
to include some config defined from Cypress in the mock server:
if (process.env.REACT_APP_ENABLE_MOCK_API === 'true') {
mockApi({
appContext: window.Cypress ? window.appContext : undefined,
database: window.Cypress ? window.database : undefined,
});
}
- Add the following in
cypress/support/commands.js
. You will need to defineMEMBERS
andCURRENT_MEMBER
to reuse them in your tests as well.
import { buildDatabase } from '@graasp/apps-query-client';
Cypress.Commands.add(
'setUpApi',
({ currentMember = CURRENT_MEMBER, database = {}, appContext } = {}) => {
// mock api and database
Cypress.on('window:before:load', (win) => {
win.database = buildDatabase({
members: Object.values(MEMBERS),
...database,
});
win.appContext = appContext;
});
},
);
- Then in all your tests you will need to set up the database and context. The default values are configured so you can easily mount an empty and operational database.
// start with an empty database
cy.setUpApi();
// start with one app data pre-saved in builder for an admin
cy.setUpApi({
database: { appData: [MOCK_APP_DATA] },
appContext: {
permission: 'admin',
context: 'builder',
},
});