Home

Things to know before testing and editing the app:

AppConfig.json: iModel configuration.
AppSetting.ts: callbacks for iModel inilization.
AppClient.ts: establish iModel backend connection and various iModel client settings.
Mapper.ts: responsible for mapping between iModel objects and our data objects.
UserEvent.ts: contains user event handlers.
ImodelEvent.ts: contains iModel event handlers.

/api: contains file that handle various callbacks and app configuration.
/components: contains React UI components that utilize functions written in /api.
/pages: a page is composed of at least one components. React-Router for navigation.

Data Object: Data from external sources are represented as Data Objects in LUmap. For example, a building data object provided by the PI System is represented by BuildingDataObject.
Matching Key: A matching key is the common value found in both iModel ecinstances and Data Objects.
Mapper: A Mapper instance is used to map iModel objects(ecinstances) to the customized objects in the app which may contain data from external resources. A Mapper typically consists of three tables: one maps an EC instance ID to a Matching Key, one maps a Matching Key to an Data Object, and one maps a Matching Key to an EC instance ID (used for handling user events).

This project was bootstrapped with Create React App.

In the project directory, you can run:

Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about deployment for more information.