Netlify allows you to clone the repository, configure the project with your own data and deploy it, all in one click.
Steps | with Yarn | with NPM |
---|---|---|
Install | yarn install |
npm install |
Run | yarn serve |
npm run serve |
SUNRISE comes with some read-only data set by default that you can use. But if you need to use a different set of data or to manage the project via Merchant Center, then you'll need to connect SUNRISE to your own commercetools project.
Once you have created your commercetools project and populated it with data, follow the next steps to connect to it.
In the Merchant Center, select your project and go to Settings
, then click on Developer Settings
section. You should now find yourself in the API Clients
tab. Click on the Create New API Client
button to display a form. There, enter a descriptive name for your new API client and select the Mobile & single-page application client
template. Once you have filled the form, submit it by clicking on Create API Client
, you should now be able to see your project credentials.
Create the file .env.local
(or any other .env
file) in the root folder of your project with the following content, replacing the data in the template (i.e. <your project key>
) for your own:
VUE_APP_CT_PROJECT_KEY=<your project key>
VUE_APP_CT_CLIENT_ID=<your client ID>
VUE_APP_CT_CLIENT_SECRET=<your client secret>
โ ๏ธ Always use an API client suited for single-page applications (SPA), as your credentials will be publicly accessible through the browser.
Optionally, you can also use a different commercetools host, instead of the default commercetools.com
(i.e. Europe). For example, to connect to our US hosts:
VUE_APP_CT_AUTH_HOST=https://auth.commercetools.co
VUE_APP_CT_API_HOST=https://api.commercetools.co
This will set up the necessary environment variables required to run SUNRISE. Feel free to choose any other approach that best suits your needs.
When executing a mutation (e.g. to update the active cart), we receive as a response the updated resource, which Apollo then uses to update the cached data in Apollo store. It is thanks to this cache that all components are able to display the same information, even after mutations.
But when we under-fetch in the mutation and fail to update some cached fields we are displaying in a component, this component will not be updated at all with any new data. To avoid that, make sure to add any field you are querying in the mutation. The update mutations are found in the methods updateMyCart
and updateMyCustomer
.
Related issue: apollographql/apollo-client#3267
The project has unit and end-to-end tests covering each functionality. Unit tests will run out of the box, but end-to-end tests require some further configuration, explained in the section below.
Test | with Yarn | with NPM |
---|---|---|
Unit | yarn test:unit |
npm run test:unit |
End-to-end | yarn test:e2e |
npm run test:e2e |
In order to continue, it is necessary that you have full control over the commercetools project associated with SUNRISE.
Follow the same steps explained in the section How to use your own project data to create a second API client, but this time create it with the Admin client
template instead. Then add your new client ID and secret as the following environment variables (e.g. in .env.local
file):
CYPRESS_CT_CLIENT_ID=<your client ID>
CYPRESS_CT_CLIENT_SECRET=<your client secret>