Development Setup

We will use this doc for development setup guidelines and FAQs.

Repo: https://github.com/egovernments/digit-ui

Use the dev branch as the base branch for the development.

Create branches as per following <bug/feature>/<JIRA ticket ID>, e.g.,

• bug/LIN-90

• feature/FSM-05

Once done with the change, create a pull request to the development branch. We will deploy and test this branch on QA and after the final QA signoff, it will be merged to the master branch with a release tag.

Clone the repo and following steps to start

Development Guidelines

Component Storybook

Please access components here https://digit-ui-internals-react-components.surge.sh

Adding or modifying modules

Modules are enabled by MDMS config at https://github.com/egovernments/egov-mdms-data/blob/DEV/data/pb/tenant/citymodule.json

To add and enable any module in the new UI, src/App.js needs to be changed.

Till PGR, we used to export Module and Links to be added to the registry, now add to the registry is part of the modules themselves. We export only the init function of the module to take care of all the initializations. So, going forward, these init functions will have to be called. We will create the init function of PGR as well. These init modules must be called after initLibraries

Changing CSS

CSS classes are published over CDN and can be seen at https://unpkg.com/@egovernments/digit-ui-css/dist/index.css

Any class can be overwritten. Please make changes in the src/index.css file.

Customizing fields in a form

First, add any new component created in the registry,

Module Specific details

• FSM: UI Implementation - Guidelines & FAQs

• PGR: UI Implementation - Guidelines & FAQs

FAQ

1. API calls are failing, what should I do?

Check src/setupProxy.js for proxy url in dev mode

2. API calls are failing with no auth token

Create a .env file with following