Merge branch 'master' of github.com:HospitalRun/hospitalrun-frontend …

…into add-translation-resources

.dockerignore

@@ -1 +1,19 @@
-node_modules
+# Items that don't need to be in a Docker image.
+# Anything not used by the build system should go here.
+.gitignore
+*.md
+*.yml
+.git
+*.js
+azure
+.editorconfig
+.github
+.npmrc
+.nvmrc
+.prettierrc
+.replit
+.vscode
+LICENSE
+docs
+*.log
+.env*

.env.example

@@ -0,0 +1 @@
+REACT_APP_HOSPITALRUN_API=http://0.0.0.0:3001

.eslintrc.js

@@ -1,4 +1,5 @@
 module.exports = {
+  ignorePatterns: ['commitlint.config.js', 'jest.config.js'],
   env: {
     browser: true,
     es6: true,
@@ -10,6 +11,7 @@ module.exports = {
     'prettier',
     'prettier/@typescript-eslint',
     'plugin:prettier/recommended',
+    'eslint-config-prettier',
   ],
   globals: {
     Atomics: 'readonly',
@@ -19,8 +21,6 @@ module.exports = {
   parserOptions: {
     project: './tsconfig.json',
     tsconfigRootDir: './',
-    // TODO: we need this because of an issue with @typescript-eslint/parser: https://github.com/typescript-eslint/typescript-eslint/issues/864
-    createDefaultProgram: true,
   },
   settings: {
     'import/resolver': {
@@ -31,6 +31,7 @@ module.exports = {
   },
   plugins: ['react', '@typescript-eslint', 'prettier', 'jest'],
   rules: {
+    'prettier/prettier': 'error',
     '@typescript-eslint/member-delimiter-style': 'off',
     '@typescript-eslint/explicit-function-return-type': 'off',
     '@typescript-eslint/no-explicit-any': 'off',

.github/CODE_OF_CONDUCT.md

@@ -1,85 +1,114 @@
-# Contributor Covenant Code of Conduct
+# Code of Conduct
 
-## Our Pledge
+HospitalRun, as a member project of OpenJS Foundation, use [Contributor Covenant v2.0](https://contributor-covenant.org/version/2/0/code_of_conduct) as their code of conduct. The full text is included [below](#contributor-covenant-code-of-conduct) in English, and translations are available from the Contributor Covenant organisation:
 
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, sex characteristics, gender identity and expression,
-level of experience, education, socio-economic status, nationality, personal
-appearance, race, religion, or sexual identity and orientation.
+- [contributor-covenant.org/translations](https://www.contributor-covenant.org/translations)
+- [github.com/ContributorCovenant](https://github.com/ContributorCovenant/contributor_covenant/tree/release/content/version/2/0)
 
-## Our Standards
+Refer to the sections on reporting and escalation in this document for the specific emails that can be used to report and escalate issues.
 
-Examples of behavior that contributes to creating a positive environment
-include:
+## Reporting
 
-- Using welcoming and inclusive language
-- Being respectful of differing viewpoints and experiences
-- Gracefully accepting constructive criticism
-- Focusing on what is best for the community
-- Showing empathy towards other community members
+### Project Spaces
 
-Examples of unacceptable behavior by participants include:
+For reporting issues in spaces related to HospitalRun please use the email `[email protected]`. HospitalRun handles CoC issues related to the spaces that they maintain. Project maintainers commit to:
 
-- The use of sexualized language or imagery and unwelcome sexual attention or
-  advances
-- Trolling, insulting/derogatory comments, and personal or political attacks
-- Public or private harassment
-- Publishing others' private information, such as a physical or electronic
-  address, without explicit permission
-- Other conduct which could reasonably be considered inappropriate in a
-  professional setting
+- maintain the confidentiality with regard to the reporter of an incident
+- to participate in the path for escalation as outlined in
+  the section on Escalation when required.
 
-## Our Responsibilities
+### Foundation Spaces
 
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
+For reporting issues in spaces managed by the OpenJS Foundation, for example, repositories within the OpenJS organization, use the email `[email protected]`. The Cross Project Council (CPC) is responsible for managing these reports and commits to:
 
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
+- maintain the confidentiality with regard to the reporter of an incident
+- to participate in the path for escalation as outlined in
+  the section on Escalation when required.
 
-## Scope
+## Escalation
 
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
+The OpenJS Foundation maintains a Code of Conduct Panel (CoCP). This is a foundation-wide team established to manage escalation when a reporter believes that a report to a member project or the CPC has not been properly handled. In order to escalate to the CoCP send an email to `[email protected]`.
 
-## Enforcement
+For more information, refer to the full
+[Code of Conduct governance document](https://github.com/openjs-foundation/bootstrap/blob/master/proposals/stage-2/CODE_OF_CONDUCT/FOUNDATION_CODE_OF_CONDUCT_REQUIREMENTS.md).
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at [email protected]. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
+---
 
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
+## Contributor Covenant Code of Conduct v2.0
 
-## Contributor License Agreement
+### Our Pledge
 
-HospitalRun is a member of the [JS Foundation](https://js.foundation/).
-As such, we request that all contributors sign the JS Foundation
-[contributor license agreement (CLA)](https://js.foundation/CLA/).
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
 
-For more information about CLAs, please check out Alex Russell’s excellent post,
-[“Why Do I Need to Sign This?”](https://infrequently.org/2008/06/why-do-i-need-to-sign-this/).
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
 
-## Attribution
+### Our Standards
 
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+Examples of behavior that contributes to a positive environment for our community include:
 
-[homepage]: https://www.contributor-covenant.org
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
 
-For answers to common questions about this code of conduct, see
-https://www.contributor-covenant.org/faq
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+### Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+### Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+### Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at the email addresses listed above in the [Reporting](#reporting) and [Escalation](#escalation) sections. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+### Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+#### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+#### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+#### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+#### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior,  harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the project community.
+
+### Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.0, available at [contributor-covenant.org/version/2/0/code_of_conduct](https://www.contributor-covenant.org/version/2/0/code_of_conduct).
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+For answers to common questions about this code of conduct, see the FAQ at
+[contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). Translations are available at [contributor-covenant.org/translations](https://www.contributor-covenant.org/translations).

.github/CONTRIBUTING.md

@@ -3,16 +3,16 @@
 HospitalRun is a community project. We invite your participation through
 financial contributions, issues, and pull requests!
 
-Contributions are always welcome. Before contributing please read the [JS Foundation's
-code of conduct](https://js.foundation/community/code-of-conduct) and
+Contributions are always welcome. Before contributing please read the [code of conduct](https://github.com/HospitalRun/hospitalrun/blob/master/.github/CODE_OF_CONDUCT.md) and
 [search the issue tracker](https://github.com/HospitalRun/hospitalrun-frontend/issues); your issue
 may have already been discussed or fixed in `master`. If you're new to the project,
 maybe you'd like to open a pull request to address one of [good-first-issue](https://github.com/HospitalRun/hospitalrun-frontend/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22).
 
 To contribute,
-[fork](https://help.github.com/articles/fork-a-repo/) HospitalRun components, commit your changes, and [send a Pull Request](https://help.github.com/articles/using-pull-requests/).
+[fork](https://help.github.com/articles/fork-a-repo/) this repo, commit your changes, and [send a Pull Request](https://help.github.com/articles/using-pull-requests/).
 
-Please note we have a [code of conduct](https://github.com/HospitalRun/hospitalrun-frontend/blob/master/.github/CODE_OF_CONDUCT.md), please follow it in all your interactions with the project.
+## Working on an Issue
+In order to optimize the workflow and to prevent multiple contributors working on the same issue without interactions, a contributor must ask to be assigned to an issue by one of the core team members: it's enough to ask it inside the specific issue.
 
 ## Feature Requests
 
@@ -39,7 +39,7 @@ Before submitting a request, please search for similar ones in the
 
 HospitalRun is a member of the [Open JS Foundation](https://openjsf.org/).
 As such, we request that all contributors sign our
-[contributor license agreement (CLA)](https://js.foundation/CLA/).
+[contributor license agreement (CLA)](https://openjsf.org/about/the-openjs-foundation-cla/).
 
 For more information about CLAs, please check out Alex Russell’s excellent post,
 [“Why Do I Need to Sign This?”](https://infrequently.org/2008/06/why-do-i-need-to-sign-this/).

.github/ISSUE_TEMPLATE.md

@@ -10,6 +10,6 @@ Issues should only be posted in this repository after you have been able to repr
 them and confirm that they are a bug or incorrect/missing information in the [docs](https://github.com/HospitalRun/hospitalrun-docs).
 
 For all other questions, requests, help resolving an issue, or if you are not sure if this is
-the right place, please do not open an issue here. Instead, try to find a solution in our [Spectrum channel](https://spectrum.chat/hospitalrun).
+the right place, please do not open an issue here. Instead, try to find a solution in our [Slack workspace](https://hospitalrun-slack.herokuapp.com/).
 
 If you have issues with the [hospitalrun.io](https://www.hospitalrun.io) site, please open an issue [here](https://github.com/HospitalRun/hospitalrun.github.io/issues).

.github/ISSUE_TEMPLATE/bug.md

@@ -1,12 +1,10 @@
 ---
-name: 🐛 Bug report
+name: "\U0001F41B Bug report"
 about: Create a report to help us improve
 title: ''
-labels: ''
+labels: bug
 assignees: ''
----
-
-Before you submit an issue we recommend you drop into our [Spectrum channel](https://spectrum.chat/hospitalrun) and ask any questions you have or mention any problems you've had getting started with HospitalRun.
+---Before you submit an issue we recommend you drop into our [Slack workspace](https://hospitalrun-slack.herokuapp.com/) and ask any questions you have or mention any problems you've had getting started with HospitalRun.
 
 **Please read this entire template before posting any issue. If you ignore these instructions
 and post an issue here that does not follow the instructions, your issue might be closed,

.github/ISSUE_TEMPLATE/config.yml

@@ -3,9 +3,6 @@ contact_links:
   - name: Feature request
     url: https://github.com/HospitalRun/hospitalrun/issues/new?template=feature.md
     about: Submit a proposal for a new feature
-  - name: Spectrum Channel
-    url: https://spectrum.chat/hospitalrun
-    about: Please ask and answer questions here.
   - name: Slack Workspace
     url: https://hospitalrun-slack.herokuapp.com/
     about: Please ask and answer questions here.

.github/ISSUE_TEMPLATE/regression.md

@@ -1,13 +1,10 @@
 ---
-name: 💥 Regression Report
+name: "\U0001F4A5 Regression Report"
 about: Report unexpected behavior that worked in previous versions
 title: ''
 labels: ''
 assignees: ''
-
----
-
-Before you submit an issue we recommend you drop into our [Spectrum channel](https://spectrum.chat/hospitalrun) and ask any questions you have or mention any problems you've had getting started with HospitalRun.
+---Before you submit an issue we recommend you drop into our [Slack workspace](https://hospitalrun-slack.herokuapp.com/) and ask any questions you have or mention any problems you've had getting started with HospitalRun.
 
 **Please read this entire template before posting any issue. If you ignore these instructions
 and post an issue here that does not follow the instructions, your issue might be closed,
@@ -30,7 +27,6 @@ Steps to reproduce the behavior:
 Paste your code here:
 
 ```js
-
 ```
 
 ## Expected behavior
@@ -40,11 +36,10 @@ A clear and concise description of what you expected to happen.
 Paste the results here:
 
 ```js
-
 ```
 
 ## Your Environment
 
-- *node version*: 6,8,10
-- *os*: Mac, Windows, Linux
-- *any other relevant information*
+- _node version_: 6,8,10
+- _os_: Mac, Windows, Linux
+- _any other relevant information_

.github/ISSUE_TEMPLATE/security.md

@@ -1,5 +1,5 @@
 ---
-name: 👮 Security Issue
+name: "\U0001F46E Security Issue"
 about: Responsible Disclosure
 title: ''
 labels: ''