Atila Client Web App

Client web app for atila.ca, demo.atila.ca and staging.atila.ca

prod:

staging:

Prerequisites

• node.js and npm

Getting Started

npm install; npm start

Open in Gitpod

Adding a Bit Component

• We use the atila-web-components-library for some of our web components
• You can add your desired component using: npm install @orgName/componentScopeName.componentID

1. npm config set '@atila:registry' https://node.bit.dev
2. npm i @atila/web-components-library.ui.crypto-payment-form or yarn add @atila/web-components-library.ui.crypto-payment-form

Steps for Adding a new Item to Redux

Taken from PR #8

• Go to src/redux/reducers/data and add a data item to a reducer in the respective .js file

• If you are creating a new reducer you will also need to add the reducer to index.js in src/redux/reducers/data

• For adding actions:

• Go to src/redux/actions/<yourActionFile>.js and add an action that will trigger that data item

• Then you can reference the redux state from mapStateToProps() and state.data.user.loggedInUserProfile

• If you are adding an action, you can do: mapDispatchToProps()

Testing

npm test

To test a specific file: npm test FileName for example: npm test Register

External APIs

This client-web app is connected to multiple external APIs

• Environment.apiUrl: atila-django: main server
• Environment.apiUrlNotion: notion-api-worker: get Wiki content from Notion
• etc.

In order to use these APIs you can either follow the instructions in the linked repos to start the service, use staging APIs instead of localhost (make sure to uncomment before pushing to avoid failed tests in CI) or mock API data (see next section).

Mock API Data

If you can't or don't want to use the actual backend API you can mock the responses.

Here are two video tutorials we made specifically on how to Mock API Data in this project.

1. How to Mock API Data in atila-client-web-app
2. How to Mock API Data in atila-client-web-app based on the request
3. How to Mock API data for use in a Pull Request

Steps:

1. Set ATILA_MOCK_API_CALLS to true in local storage.

   1. Right click in your browser > Inspect > Application.

2. Get the JSON response of the data you want to mock.

   1. This can usually be retrieved from staging.atila.ca and checking the network tap of the request using devtools.
   2. Right click > Inspect > Network and filter by the api URL.
   3. Use jsonformatter.curiousconcept.com to add tab spacing to make your JSON files easier to read and so it's not one one line
      1. Make sure to use a 4 space tab
   4. Note: Make sure you don't use production data containing private information for your mock data:
      1. For example, if you want to mock a list of applications or a user profile, ask someone else on the team to send your some mock data on their local dev environment and provide them with the url you are trying to mock

3. Copy that JSON response and put it into src/services/mocks/{Object_name}/{File_name}.json for example if you wanted to make a scholarship list response you would put it into src/services/mocks/Scholarship/ScholarshipsPreview1.json you might have to make a new directory if the object name you want to use doesn't exist.

4. Go to MockAPI.initializeMocks() in src/services/mocks/MockAPI.js to add the instructions for how to mock your new data.

We use axios-mock-adapter for our API mocking, see their documentation for how to do more advanced mocking such as returning a certain response based on the request parameters.

Note: You can only mock api calls in the dev environment.

Storybook

• We use Storybook to develop components independently from business logic, see Adding Storybook to our Web App Development Process

• To run Storybook:

  • You only have to do this the first time you run Storybook: delete node_modules and package-lock.json NOT package.json then run npm install
  • npm run storybook
  • If that command fails with:

  Error: EEXIST: file already exists, mkdir '/Users/admin/Desktop/tomiwa/codeproj/atila-code/atila-client-web-app/node_modules/.cache/ts-docgen'
  

  • Try running npm run storybook:clear-cache
  • You can run your react server alongside storybook: Open a seperate terminal window and run npm start

• To add a new component to Storybook: create it in src/stories/{ComponentName}.stories.js

• Follow the example in src/stories/ContentCard.stories.js and create a seperate story for each scenario of that component

• NOTE: if there is an error in one of your components, instead of storybook crashing, the error is displayed in the console so make sure to inpect console to see the error

• Learn more here:

  • https://storybook.js.org/docs/react/get-started/introduction
  • https://storybook.js.org/docs/react/writing-stories/introduction

How to Create a Pull Request

• Read/Watch: How we Write Frontend React Code and Create Pull Requests at Atila

• Watch: How to Get the Unique Deploy URL for a Code Push

Deployment

This project deploys to 3 environments using Netlify

• master deploys to atila.ca

• demo deploys to demo.atila.ca

• All other branches that are not master or demo deploy to staging.atila.ca

• To push to demo branch and trigger a deploy to demo.atla.ca from CI run: git push origin <local_branch_name>:demo

• The environment variables for these domains are in circleci: https://app.circleci.com/settings/project/github/ademidun/atila-client-web-app/environment-variables

Troubleshooting

• If you get compiler errors in your IDE, try setting your Typescript version:
  • https://stackoverflow.com/a/64969461/5405197