Merge pull request #4 from OHIF/v3-stable

V3 stable

.docker/Nginx-Orthanc/docker-compose.yml

@@ -2,7 +2,7 @@ version: '3.5'
 
 services:
   orthanc:
-    image: jodogne/orthanc-plugins:1.5.7
+    image: jodogne/orthanc-plugins:1.11.0
     hostname: orthanc
     volumes:
       # Config

.github/FUNDING.yml

@@ -0,0 +1 @@
+custom: https://giving.massgeneral.org/ohif

.github/ISSUE_TEMPLATE/bug-report.yml

@@ -0,0 +1,86 @@
+name: 'Bug report'
+description: Create a report to help us improve
+title: '[Bug] '
+labels: ['Community: Report :bug:', 'Awaiting Reproduction']
+
+body:
+  - type: markdown
+    attributes:
+      value: |
+        👋 Hello, and thank you for contributing to our project! Your support is greatly appreciated.
+
+        🔍 Before proceeding, please make sure to read our [Rules of Conduct](https://github.com/OHIF/Viewers/blob/master/CODE_OF_CONDUCT.md) and familiarize yourself with our [development process](https://v3-docs.ohif.org/development/our-process).
+
+        ❓ If you're here to seek general support or ask a question, we encourage you to visit our [community discussion board](https://community.ohif.org/)
+
+        🐞 For bug reports, please complete the following template in as much detail as possible. This will help us reproduce and address the issue efficiently.
+
+        🧪 Finally, ensure that you're using the latest version of the software and check if your issue has already been reported to avoid duplicates.
+
+  - type: textarea
+    id: bug_description
+    attributes:
+      label: Describe the Bug
+      description: 'A clear and concise description of what the bug is.'
+    validations:
+      required: true
+
+  - type: textarea
+    id: reproduction_steps
+    attributes:
+      label: Steps to Reproduce
+      description: 'Please describe the steps to reproduce the issue.'
+      placeholder: "1. First step\n2. Second step\n3. ..."
+    validations:
+      required: true
+
+  - type: textarea
+    id: current_behavior
+    attributes:
+      label: The current behavior
+      description:
+        'A clear and concise description of what happens instead of the expected
+        behavior.'
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected_behavior
+    attributes:
+      label: The expected behavior
+      description:
+        'A clear and concise description of what you expected to happen.'
+    validations:
+      required: true
+
+  - type: input
+    id: os
+    attributes:
+      label: 'OS'
+      description: 'Your operating system.'
+      placeholder: 'e.g., Windows 10, macOS 10.15.4'
+    validations:
+      required: true
+  - type: input
+    id: node-version
+    attributes:
+      label: 'Node version'
+      description: 'Your Node.js version.'
+      placeholder: 'e.g., 16.14.0'
+    validations:
+      required: true
+  - type: input
+    id: browser
+    attributes:
+      label: 'Browser'
+      description: 'Your browser.'
+      placeholder: 'e.g., Chrome 83.0.4103.116, Firefox 77.0.1, Safari 13.1.1'
+    validations:
+      required: true
+
+  - type: markdown
+    attributes:
+      value: >
+        > :warning: Reports we cannot reproduce are at risk of being marked
+        stale and > closed. The more information you can provide, the more
+        likely we are to look > into and address your issue.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: 🤗 Support Question
+    url: https://community.ohif.org/
+    about: Please use our forum if you have questions or need help.

.github/ISSUE_TEMPLATE/feature-request.yml

@@ -0,0 +1,36 @@
+name: Feature request
+description: Create a feature request
+labels: ['Community: Request :hand:']
+title: '[Feature Request] '
+body:
+  - type: markdown
+    attributes:
+      value: |
+        👋 Hello and thank you for your interest in our project!
+
+        🔍 Before you proceed, please read our [Rules of Conduct](https://github.com/OHIF/Viewers/blob/master/CODE_OF_CONDUCT.md).
+
+        🚀 If your request is specific to your needs, consider contributing it yourself! Read our [contributing guides](https://v3-docs.ohif.org/development/contributing) to get started.
+
+        🖊️ Please provide as much detail as possible for your feature request. Mock-up screenshots, workflow or logic flow diagrams are very helpful. Discuss how your requested feature would interact with existing features.
+
+        ⏱️ Lastly, tell us why we should prioritize your feature. What impact would it have?
+
+  - type: textarea
+    attributes:
+      label: 'What feature or change would you like to see made?'
+      description:
+        'Please include as much detail as possible including possibly mock up
+        screen shots, workflow or logic flow diagrams etc.'
+      placeholder: '...'
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: 'Why should we prioritize this feature?'
+      description:
+        'Discuss if and how the requested feature interacts with existing
+        features.'
+      placeholder: '...'
+    validations:
+      required: true

.github/pull_request_template.md

@@ -1,14 +1,91 @@
-### PR Checklist
+<!-- Do Not Delete This! pr_template -->
+<!-- Please read our Rules of Conduct: https://github.com/OHIF/Viewers/blob/master/CODE_OF_CONDUCT.md -->
+<!-- 🕮 Read our guide about our Contributing Guide here https://v3-docs.ohif.org/development/contributing -->
+<!-- :hand: Thank you for starting this amazing contribution! -->
 
-- [ ] Brief description of changes
-- [ ] Links to any relevant issues
-- [ ] Required status checks are passing
-- [ ] User cases if changes impact the user's experience
-- [ ] `@mention` a maintainer to request a review
+<!--
+⚠️⚠️ Please make sure the checklist section below is complete before submitting your PR.
+To complete the checklist, add an 'x' to each item: [] -> [x]
+(PRs that do not have all the checkboxes marked will not be approved)
+-->
+
+### Context
+
+<!--
+Provide a clear explanation of the reasoning behind this change, such as:
+- A link to the issue being addressed, using the format "Fixes #ISSUE_NUMBER"
+- An image showing the issue or problem being addressed (if not already in the issue)
+- Error logs or callStacks to help with the understanding of the problem (if not already in the issue)
+-->
+
+### Changes & Results
+
+<!--
+List all the changes that have been done, such as:
+- Add new components
+- Remove old components
+- Update dependencies
+
+What are the effects of this change?
+- Before vs After
+- Screenshots / GIFs / Videos
+-->
+
+### Testing
+
+<!--
+Describe how we can test your changes.
+- open a URL
+- visit a page
+- click on a button
+- etc.
+-->
+
+### Checklist
+
+#### PR
 
 <!--
-  Links
-  -->
+https://semantic-release.gitbook.io/semantic-release/#how-does-it-work
+
+Examples:
+Please note the letter casing in the provided examples (upper or lower).
+
+- feat(MeasurementService): add ...
+- fix(Toolbar): fix ...
+- docs(Readme): update ...
+- style(Whitespace): fix ...
+- refactor(ExtensionManager): ...
+- test(HangingProtocol): Add test ...
+- chore(git): update ...
+- perf(VolumeLoader): ...
+
+You don't need to have each commit within the Pull Request follow the rule,
+but the PR title must comply with it, as it will be used as the commit message
+after the commits are squashed.
+-->
+
+- [] My Pull Request title is descriptive, accurate and follows the
+  semantic-release format and guidelines.
+
+#### Code
+
+- [] My code has been well-documented (function documentation, inline comments,
+  etc.)
+
+#### Public Documentation Updates
+
+<!-- https://v3-docs.ohif.org/ -->
+
+- [] The documentation page has been updated as necessary for any public API
+  additions or removals.
+
+#### Tested Environment
+
+- [] OS: <!--[e.g. Windows 10, macOS 10.15.4]-->
+- [] Node version: <!--[e.g. 16.14.0]-->
+- [] Browser:
+  <!--[e.g. Chrome 83.0.4103.116, Firefox 77.0.1, Safari 13.1.1]-->
 
 <!-- prettier-ignore-start -->
 [blog]: https://circleci.com/blog/triggering-trusted-ci-jobs-on-untrusted-forks/

.github/stale.yml

@@ -2,25 +2,19 @@
 # https://github.com/apps/stale
 #
 # Number of days of inactivity before an issue becomes stale
-daysUntilStale: 21
+daysUntilStale: 180
 # Number of days of inactivity before a stale issue is closed
-daysUntilClose: 7
+daysUntilClose: 60
 # Issues with these labels will never be considered stale
 exemptLabels:
-  - 'Story :raised_hands:'
   - 'Bug: Verified :bug:'
-  - 'Task: CI/Tooling :robot:'
-  - 'Task: Docs 📖'
-  - 'Task: Docs :book:'
-  - 'Task: Refactor :hammer_and_wrench:'
-  - 'Task: Tests :microscope:'
   - 'PR: Awaiting Review 👀'
-  - 'Triage :white_flag:'
-  - 'Extension: Discussion'
   - 'Announcement 🎉'
   - 'IDC:priority'
   - 'IDC:candidate'
   - 'IDC:collaboration'
+  - 'Community: Request :hand:'
+  - 'Community: Report :bug:'
 # Label to use when marking an issue as stale
 staleLabel: 'Stale :baguette_bread:'
 # Comment to post when marking an issue as stale. Set to `false` to disable

.webpack/rules/transpileJavaScript.js

@@ -25,13 +25,15 @@ function transpileJavaScript(mode) {
     // These are packages that are not transpiled to our lowest supported
     // JS version (currently ES5). Most of these leverage ES6+ features,
     // that we need to transpile to a different syntax.
-    exclude,
+    exclude: [/(codecs)/, /(dicomicc)/, exclude],
     loader: 'babel-loader',
     options: {
       // Find babel.config.js in monorepo root
       // https://babeljs.io/docs/en/options#rootmode
       rootMode: 'upward',
       envName: mode,
+      cacheCompression: false,
+      cacheDirectory: true,
     },
   };
 }