Update master to main (#497)

Author: ZacButko

.github/pull_request_template.md

@@ -6,7 +6,7 @@
 
 #### If applicable
 - [ ] My work includes tests or is validated by existing tests.
-- [ ] I have updated the [esm-framework mock](https://github.com/openmrs/openmrs-esm-core/blob/master/packages/framework/esm-framework/mock.tsx) to reflect any API changes I have made.
+- [ ] I have updated the [esm-framework mock](https://github.com/openmrs/openmrs-esm-core/blob/main/packages/framework/esm-framework/mock.tsx) to reflect any API changes I have made.
 
 ## Summary
 <!-- Please describe what problems your PR addresses. -->

.github/workflows/ci.yml

@@ -3,9 +3,9 @@ name: OpenMRS CI
 on:
   workflow_dispatch: # temporary, for debugging
   push:
-    branches: [master]
+    branches: [main]
   pull_request:
-    branches: [master]
+    branches: [main]
   release:
     types:
       - created
@@ -25,11 +25,11 @@ jobs:
 
       - name: Cache dependencies
         id: cache
-        uses: actions/cache@v3 
+        uses: actions/cache@v3
         with:
           path: '**/node_modules'
           key: ${{ runner.os }}-${{ hashFiles('**/yarn.lock') }}
-      
+
       - name: Install dependencies
         if: steps.cache.outputs.cache-hit != 'true'
         run: yarn
@@ -39,10 +39,10 @@ jobs:
         with:
           repo-token: ${{ secrets.GITHUB_TOKEN }}
           server-token: ${{ secrets.TURBO_SERVER_TOKEN }}
-      
+
       - name: Run lint, tests and typecheck code
-        run: yarn run verify 
-      
+        run: yarn run verify
+
       - name: Run build
         run: yarn turbo run build --color --api="http://127.0.0.1:9080" --token="${{ secrets.TURBO_SERVER_TOKEN }}" --team="${{ github.repository_owner }}"
 
@@ -60,14 +60,14 @@ jobs:
         with:
           node-version: "16.15"
           registry-url: "https://registry.npmjs.org"
-      
+
       - name: Cache dependencies
         id: cache
-        uses: actions/cache@v3 
+        uses: actions/cache@v3
         with:
           path: '**/node_modules'
           key: ${{ runner.os }}-${{ hashFiles('**/yarn.lock') }}
-      
+
       - name: Install dependencies
         if: steps.cache.outputs.cache-hit != 'true'
         run: yarn
@@ -136,11 +136,11 @@ jobs:
 
       - name: Cache dependencies
         id: cache
-        uses: actions/cache@v3 
+        uses: actions/cache@v3
         with:
           path: '**/node_modules'
           key: ${{ runner.os }}-${{ hashFiles('**/yarn.lock') }}
-      
+
       - name: Install dependencies
         if: steps.cache.outputs.cache-hit != 'true'
         run: yarn

.github/workflows/docs.yml

@@ -2,9 +2,9 @@ name: Check documentation
 
 on:
   push:
-    branches: [master]
+    branches: [main]
   pull_request:
-    branches: [master]
+    branches: [main]
   schedule:
     - cron: "0 9 * * *"
 

.github/workflows/size.yml

@@ -2,7 +2,7 @@ name: Report bundle size
 
 on:
   pull_request_target:
-    branches: [master]
+    branches: [main]
 
 jobs:
   file_size_impact:

.husky/pre-commit

@@ -5,4 +5,4 @@ set -e  # die on error
 
 yarn run extract-translations
 yarn pretty-quick --staged
-yarn lerna run document --since master
+yarn lerna run document --since main

README.md

@@ -155,7 +155,7 @@ to indicate big new features and breaking changes, and patch changes (e.g. `3.2.
 otherwise.
 
 Note that this command will not create a new tag, nor publish the packages.
-After running it, make a PR or merge to `master` with the resulting changeset.
+After running it, make a PR or merge to `main` with the resulting changeset.
 
 Once the version bump is merged, go to GitHub and
 [draft a new release](https://github.com/openmrs/openmrs-esm-core/releases/new). 

docs/getting_started/release_and_deployment.md

@@ -6,13 +6,13 @@ Distributions use frontend modules which are published as packages in NPM.
 Those distributions can refer to frontend module versions by number (e.g. `3.1.0`)
 or by tag (e.g. `latest`).
 
-GitHub Actions is used to publish frontend modules from the `master` branch
+GitHub Actions is used to publish frontend modules from the `main` branch
 to the `next` tag.
 You can see the published versions of each frontend module on npmjs.com. See for example
 [@openmrs/esm-login-app](https://www.npmjs.com/package/@openmrs/esm-login-app?activeTab=versions).
 The [OpenMRS CI server](https://dev3.openmrs.org/openmrs/spa/login)
 always shows the `next` version of all frontend modules (i.e., the latest from the
-`master` branch).
+`main` branch).
 
 You can version a frontend module by creating a release in GitHub. This will trigger
 GitHub Actions to publish a new version of the package with the `latest` tag.

docs/getting_started/setup.md

@@ -104,7 +104,7 @@ the import map overrides panel to override the existing import map
 entry, or add your frontend module as a new entry.
 
 For example, if you run `yarn serve` in
-[esm-login-app](https://github.com/openmrs/openmrs-esm-core/tree/master/packages/apps/esm-login-app),
+[esm-login-app](https://github.com/openmrs/openmrs-esm-core/tree/main/packages/apps/esm-login-app),
 and if it says something like `Project is running at http://localhost:8080/`,
 as well as something like `asset openmrs-esm-login-app.js`, then in the import
 map overrides you can click on the entry for `openmrs-esm-login-app` and give it the value

docs/index.html

@@ -23,7 +23,7 @@
       subMaxLevel: 1,
       relativePath: true,
       plugins: [
-        EditOnGithubPlugin.create("https://github.com/openmrs/openmrs-esm-core/edit/master/docs/")
+        EditOnGithubPlugin.create("https://github.com/openmrs/openmrs-esm-core/edit/main/docs/")
       ]
     }
   </script>

docs/main/config.md

@@ -148,7 +148,7 @@ colorPicker: {
 ```
 
 For convenience, some common validators are provided out of the box. See the
-[API / validators](https://github.com/openmrs/openmrs-esm-core/blob/master/packages/framework/esm-framework/docs/API.md#validators).
+[API / validators](https://github.com/openmrs/openmrs-esm-core/blob/main/packages/framework/esm-framework/docs/API.md#validators).
 
 #### Arrays
 
@@ -229,7 +229,7 @@ the defaults for configuration elements for which no values have been provided.
 
 A React Hook is provided to hide the asynchronicity of config loading. The
 `moduleName`provided to the
-[`openmrsComponentDecorator` in esm-react-utils](https://github.com/openmrs/openmrs-esm-core/tree/master/packages/framework/esm-react-utils)
+[`openmrsComponentDecorator` in esm-react-utils](https://github.com/openmrs/openmrs-esm-core/tree/main/packages/framework/esm-react-utils)
 is used to look up the configuration elsewhere in the application.
 
 ```js
@@ -301,7 +301,7 @@ the element, but this may change in future versions.
 
 #### `_type`
 
-One of the values from [the `Type` enum](https://github.com/openmrs/openmrs-esm-core/blob/master/packages/framework/esm-framework/docs/enums/Type.md). Used for validation and to help the
+One of the values from [the `Type` enum](https://github.com/openmrs/openmrs-esm-core/blob/main/packages/framework/esm-framework/docs/enums/Type.md). Used for validation and to help the
 implementer tools work with the element.
 
 Should always appear alongside `_default`.
@@ -318,10 +318,10 @@ Can be used anywhere within the schema structure.
 An array of validator objects.
 
 Some common validators are
-provided: [API / validators](https://github.com/openmrs/openmrs-esm-core/blob/master/packages/framework/esm-framework/docs/API.md#config-validation-functions).
+provided: [API / validators](https://github.com/openmrs/openmrs-esm-core/blob/main/packages/framework/esm-framework/docs/API.md#config-validation-functions).
 
 Custom validators should
-be created with the [validator](https://github.com/openmrs/openmrs-esm-core/blob/master/packages/framework/esm-framework/docs/API.md#validator) function.
+be created with the [validator](https://github.com/openmrs/openmrs-esm-core/blob/main/packages/framework/esm-framework/docs/API.md#validator) function.
 
 Can be used anywhere within the schema structure.
 
@@ -333,7 +333,7 @@ contained in the array.
 
 ## API Documentation
 
-See the Config Functions section of the [API docs](https://github.com/openmrs/openmrs-esm-core/blob/master/packages/framework/esm-framework/docs/API.md).
+See the Config Functions section of the [API docs](https://github.com/openmrs/openmrs-esm-core/blob/main/packages/framework/esm-framework/docs/API.md).
 
 ## The RFC
 

docs/main/data.md

@@ -14,12 +14,12 @@ Some data is available using higher-level functions or custom React Hooks provid
 by `@openmrs/esm-framework`.  These should be used when available.
 
 All of this functionality (React hooks excepted) is provided by the
-[`@openmrs/esm-api`](https://github.com/openmrs/openmrs-esm-core/tree/master/packages/framework/esm-api)
+[`@openmrs/esm-api`](https://github.com/openmrs/openmrs-esm-core/tree/main/packages/framework/esm-api)
 package, which is part of `@openmrs/esm-framework`.
 The React hooks are in
-[`@openmrs/esm-react-utils`](https://github.com/openmrs/openmrs-esm-core/blob/master/packages/framework/esm-react-utils),
+[`@openmrs/esm-react-utils`](https://github.com/openmrs/openmrs-esm-core/blob/main/packages/framework/esm-react-utils),
 which is also part of `@openmrs/esm-framework`. See the
-[API Docs](https://github.com/openmrs/openmrs-esm-core/blob/master/packages/framework/esm-framework/docs/API.md).
+[API Docs](https://github.com/openmrs/openmrs-esm-core/blob/main/packages/framework/esm-framework/docs/API.md).
 
 ## FHIR
 
@@ -39,7 +39,7 @@ If you have questions about FHIR support in OpenMRS, you can ask in the
 
 Some administrative endpoints will likely never have a proper representation in FHIR (e.g., endpoints for managing encounter types). When no suitable FHIR endpoint is available, you will want to use a different OpenMRS server API. The [REST Web Services API](https://rest.openmrs.org/) is used widely across many of our frontend modules.
 
-We recommend using [SWR](https://swr.vercel.app/docs/data-fetching) based hooks and the [`openmrsFetch`](https://github.com/openmrs/openmrs-esm-core/blob/master/packages/framework/esm-framework/docs/API.md#openmrsfetch) fetcher function to retrieve data from the server. SWR offers a host of features that help us deliver an improved user experience.
+We recommend using [SWR](https://swr.vercel.app/docs/data-fetching) based hooks and the [`openmrsFetch`](https://github.com/openmrs/openmrs-esm-core/blob/main/packages/framework/esm-framework/docs/API.md#openmrsfetch) fetcher function to retrieve data from the server. SWR offers a host of features that help us deliver an improved user experience.
 
 Here's an example of a custom SWR hook that retrieves visits data.
 
@@ -131,6 +131,6 @@ Some API objects are made available via React hooks (or via framework-agnostic s
 The hooks are in
 `@openmrs/esm-react-utils`,
 and the subscription-yielding equivalents are in
-[`@openmrs/esm-api`](https://github.com/openmrs/openmrs-esm-core/blob/master/packages/framework/esm-framework/docs/API.md#api-functions).
-See for example [`useVisitTypes`](https://github.com/openmrs/openmrs-esm-core/blob/master/packages/framework/esm-framework/docs/API.md#usevisittypes)
-and the corresponding [`getVisitTypes`](https://github.com/openmrs/openmrs-esm-core/blob/master/packages/framework/esm-framework/docs/API.md#getvisittypes).
+[`@openmrs/esm-api`](https://github.com/openmrs/openmrs-esm-core/blob/main/packages/framework/esm-framework/docs/API.md#api-functions).
+See for example [`useVisitTypes`](https://github.com/openmrs/openmrs-esm-core/blob/main/packages/framework/esm-framework/docs/API.md#usevisittypes)
+and the corresponding [`getVisitTypes`](https://github.com/openmrs/openmrs-esm-core/blob/main/packages/framework/esm-framework/docs/API.md#getvisittypes).

docs/main/dates.md

@@ -8,9 +8,9 @@ are intended to accomodate that variation.
 ## Formatting for display
 
 Date objects can be displayed in a variety of standard formats using the
-[formatDate](https://github.com/openmrs/openmrs-esm-core/blob/master/packages/framework/esm-framework/docs/API.md#formatdate),
-[formatTime](https://github.com/openmrs/openmrs-esm-core/blob/master/packages/framework/esm-framework/docs/API.md#formattime), and
-[formatDatetime](https://github.com/openmrs/openmrs-esm-core/blob/master/packages/framework/esm-framework/docs/API.md#formatdatetime)
+[formatDate](https://github.com/openmrs/openmrs-esm-core/blob/main/packages/framework/esm-framework/docs/API.md#formatdate),
+[formatTime](https://github.com/openmrs/openmrs-esm-core/blob/main/packages/framework/esm-framework/docs/API.md#formattime), and
+[formatDatetime](https://github.com/openmrs/openmrs-esm-core/blob/main/packages/framework/esm-framework/docs/API.md#formatdatetime)
 functions. These functions format dates in ways that are both adaptable
 (using the `mode` parameter) and localized according to the user's locale.
 
@@ -28,7 +28,7 @@ formatted into ISO-8601 format.
 
 The ISO-8601 date strings sent by the server can be parsed into Javascript
 `Date` objects using the
-[parseDate](https://github.com/openmrs/openmrs-esm-core/blob/master/packages/framework/esm-framework/docs/API.md#parsedate)
+[parseDate](https://github.com/openmrs/openmrs-esm-core/blob/main/packages/framework/esm-framework/docs/API.md#parsedate)
 function. This uses [dayjs](https://day.js.org/docs/en/parse/string) for
 parsing.
 

docs/main/extensions.md

@@ -24,7 +24,7 @@ Read the above two lines until they resonate in your head like a mantra.
 Extensions get rendered into slots. An extension gets associated with a
 slot in one of the following ways:
 - The extension names the slot in its definition, under `slot[s]`
-- A call to [attach](https://github.com/openmrs/openmrs-esm-core/blob/master/packages/framework/esm-framework/docs/API.md#attach)
+- A call to [attach](https://github.com/openmrs/openmrs-esm-core/blob/main/packages/framework/esm-framework/docs/API.md#attach)
 - A system administrator adds the extension to the slot using the
   slot's `add` array
 
@@ -58,10 +58,10 @@ Extensions are defined in the `setupOpenMRS` function of a module, in an
 `extensions` array. Each element of this array defines an extension, with
 a name and a load function. It may also specify the names of slots to
 attach the extension to by default. It may also specify
-[a number of other things](https://github.com/openmrs/openmrs-esm-core/blob/master/packages/framework/esm-framework/docs/interfaces/ExtensionDefinition.md),
+[a number of other things](https://github.com/openmrs/openmrs-esm-core/blob/main/packages/framework/esm-framework/docs/interfaces/ExtensionDefinition.md),
 some of which will be covered below.
 
-Slots are components. There is an [ExtensionSlot](https://github.com/openmrs/openmrs-esm-core/blob/master/packages/framework/esm-framework/docs/API.md#extensionslot)
+Slots are components. There is an [ExtensionSlot](https://github.com/openmrs/openmrs-esm-core/blob/main/packages/framework/esm-framework/docs/API.md#extensionslot)
 React component. If you are working in a different framework and would like to create
 an extension slot, please get in touch with the OpenMRS Frontend 3.0 team
 on Slack.
@@ -153,7 +153,7 @@ information.
 State is provided as a parameter to the `ExtensionSlot` or `Extension`
 components, and recieved as a prop by the extension.
 
-See the [ExtensionSlot API docs](https://github.com/openmrs/openmrs-esm-core/blob/master/packages/framework/esm-framework/docs/API.md#extensionslot)
+See the [ExtensionSlot API docs](https://github.com/openmrs/openmrs-esm-core/blob/main/packages/framework/esm-framework/docs/API.md#extensionslot)
 for more.
 
 ## Meta
@@ -168,7 +168,7 @@ Meta is provided by extensions in their definition in the `setupOpenMRS`
 function.
 
 Slots can access meta through the extension system API, such as by using
-[useExtensionSlotMeta](https://github.com/openmrs/openmrs-esm-core/blob/master/packages/framework/esm-framework/docs/API.md#useextensionslotmeta).
+[useExtensionSlotMeta](https://github.com/openmrs/openmrs-esm-core/blob/main/packages/framework/esm-framework/docs/API.md#useextensionslotmeta).
 
 ## Offline Support
 

docs/main/state.md

@@ -13,14 +13,14 @@ This can come up, for example, if you your frontend module has multiple extensio
 that need to share state with each other.
 
 In these cases you can use the
-[`@openmrs/esm-state`](https://github.com/openmrs/openmrs-esm-core/tree/master/packages/framework/esm-state)
+[`@openmrs/esm-state`](https://github.com/openmrs/openmrs-esm-core/tree/main/packages/framework/esm-state)
 features of `@openmrs/esm-framework`. The framework provides functions for
 managing state using [Unistore](https://github.com/developit/unistore#unistore).
 
 ## How do I use it?
 
 A Unistore store can be created using
-[`createGlobalStore`](https://github.com/openmrs/openmrs-esm-core/blob/master/packages/framework/esm-framework/docs/API.md#createglobalstore):
+[`createGlobalStore`](https://github.com/openmrs/openmrs-esm-core/blob/main/packages/framework/esm-framework/docs/API.md#createglobalstore):
 
 ```typescript
 import { createGlobalStore } from '@openmrs/esm-framework';
@@ -35,7 +35,7 @@ createGlobalStore("books", {
 ```
 
 The store can then be accessed using
-[`getGlobalStore`](https://github.com/openmrs/openmrs-esm-core/blob/master/packages/framework/esm-framework/docs/API.md#getglobalstore)
+[`getGlobalStore`](https://github.com/openmrs/openmrs-esm-core/blob/main/packages/framework/esm-framework/docs/API.md#getglobalstore)
 
 ```typescript
 import { getGlobalStore } from '@openmrs/esm-framework';

docs/under_the_hood/architecture.md

@@ -24,7 +24,7 @@ Once the UI is rendered the content is exclusively coming from the different fro
 Frontend modules use [dynamic imports](https://webpack.js.org/guides/code-splitting/)
 to split into a "front bundle" and content bundles.
 The front bundle begins at the entry point, which the
-[webpack config](https://github.com/openmrs/openmrs-esm-core/blob/master/packages/tooling/openmrs/default-webpack-config.js)
+[webpack config](https://github.com/openmrs/openmrs-esm-core/blob/main/packages/tooling/openmrs/default-webpack-config.js)
 takes from the
 [main entry of package.json](https://github.com/openmrs/openmrs-esm-template-app/blob/69b0f7a3ef3e79e9851fc0621e8b6c8311e7e6d7/package.json#L7)
 and which is usually `src/index.ts`. This bundle should be small and not contain much

docs/under_the_hood/squad_devops.md

@@ -1,10 +1,10 @@
 # Squad DevOps and CI
 
 The CI server at dev3.openmrs.org is a community resource, hosted on the OpenMRS infrastructure, though the actual ESMs are stored in a Digital Ocean space kindly provided by AMPATH. Every time a commit is made to
-`master` in a community-managed frontend module repository, GitHub Actions
+`main` in a community-managed frontend module repository, GitHub Actions
 deploys the built package to Digital Ocean and updates the importmap so that the CI server always runs the latest version of all modules.
 
-Every time a GitHub release is created in a community-managed frontend module repository, GitHub Actions releases a new NPM package for each frontend module (tag: "latest"). The difference to an ordinary commit to `master` is that these only create preview packages (tag: "next").
+Every time a GitHub release is created in a community-managed frontend module repository, GitHub Actions releases a new NPM package for each frontend module (tag: "latest"). The difference to an ordinary commit to `main` is that these only create preview packages (tag: "next").
 
 [OpenMRS Bamboo](https://ci.openmrs.org/allPlans.action) is used only for
 [openmrs-module-spa](https://github.com/openmrs/openmrs-module-spa/). Its jobs