Initial Commit

.babelrc.json

@@ -0,0 +1,14 @@
+{
+  "presets": [
+    [
+      "@nrwl/react/babel",
+      {
+        "runtime": "automatic",
+        "useBuiltIns": "usage"
+      }
+    ]
+  ],
+  "plugins": [["@babel/plugin-proposal-class-properties", {"loose":  false}],
+    ["@babel/plugin-proposal-private-methods", {"loose":  false}],
+    ["@babel/plugin-proposal-private-property-in-object", {"loose":  false}]]
+}

.eslintrc.json

@@ -0,0 +1,35 @@
+{
+  "root": true,
+  "ignorePatterns": ["**/*"],
+  "plugins": ["@nrwl/nx"],
+  "overrides": [
+    {
+      "files": ["*.ts", "*.tsx", "*.js", "*.jsx"],
+      "rules": {
+        "@nrwl/nx/enforce-module-boundaries": [
+          "error",
+          {
+            "enforceBuildableLibDependency": true,
+            "allow": [],
+            "depConstraints": [
+              {
+                "sourceTag": "*",
+                "onlyDependOnLibsWithTags": ["*"]
+              }
+            ]
+          }
+        ]
+      }
+    },
+    {
+      "files": ["*.ts", "*.tsx"],
+      "extends": ["plugin:@nrwl/nx/typescript"],
+      "rules": {}
+    },
+    {
+      "files": ["*.js", "*.jsx"],
+      "extends": ["plugin:@nrwl/nx/javascript"],
+      "rules": {}
+    }
+  ]
+}

.github/ISSUE_TEMPLATE/01_bugReport.md

@@ -0,0 +1,49 @@
+---
+name: Bug report
+about: Report a bug in Tiller
+title: ""
+labels: "bug"
+assignees: ""
+---
+
+<!--
+  Please use Markdown syntax throughout the report for improved clarity.
+  https://guides.github.com/features/mastering-markdown/
+
+  Feel free to remove any section in the template that is not relevant or needed for your report.
+  However, keep in mind that filling out those sections can significantly reduce resolution duration.
+-->
+
+## Basic information
+
+* Tiller version:
+  <!-- released version -->
+* Module:
+  <!-- Please, include name(s) of relevant Tiller's module(s). If not related to any specific module, specify "project" instead. -->
+* Link to the complete executable reproducer if available (e.g. GitHub Repo):
+
+## Additional information
+
+<!-- Please, include any additional information that could be relevant (e.g. npm/yarn, OS version). -->
+
+## Bug description
+
+<!--
+  Please, describe the bug as clear and concisely as possible.
+  If relevant and possible, also fill out the sub-sections below.
+-->
+
+### Steps to reproduce
+
+<!-- Please, share all steps to reproduce the bug. -->
+
+### Expected behavior
+
+<!-- Please, describe the expected behavior. -->
+
+### Actual behavior
+
+<!--
+  Please, describe the actual behavior as discovered.
+  If available, provide the entire stack trace inside Markdown code block (```).
+-->

.github/ISSUE_TEMPLATE/02_enhancementRequest.md

@@ -0,0 +1,42 @@
+---
+name: Enhancement request
+about: Suggest an enhancement to an existing feature for Tiller
+title: ""
+labels: "enhancement"
+assignees: ""
+---
+
+<!--
+  Please use Markdown syntax throughout the report for improved clarity.
+  https://guides.github.com/features/mastering-markdown/
+-->
+
+## Basic information
+
+* Tiller version:
+  <!-- released version -->
+* Module:
+  <!-- Please, include name(s) of relevant Tiller's module(s). If not related to any specific module, specify "project" instead. -->
+
+## Additional information
+
+<!-- Please, include any additional information that could be relevant (e.g. npm/yarn, OS version). -->
+
+## Enhancement description
+
+<!--
+  Please, describe the enhancement you envision.
+  If relevant and possible, also fill out the sub-sections below.
+-->
+
+### Current behaviour
+
+<!-- Please, provide the current behavior around this topic, if applicable. -->
+
+### Wanted behaviour
+
+<!-- Please, describe the desired outcome around the suggested enhancement. -->
+
+### Possible workarounds
+
+<!-- Please, share any workarounds for the described enhancement, if applicable. -->

.github/ISSUE_TEMPLATE/03_featureRequest.md

@@ -0,0 +1,42 @@
+---
+name: Feature request
+about: Suggest a new feature for Tiller
+title: ""
+labels: "feature"
+assignees: ""
+---
+
+<!--
+  Please use Markdown syntax throughout the report for improved clarity.
+  https://guides.github.com/features/mastering-markdown/
+-->
+
+## Basic information
+
+* Tiller version:
+  <!-- released version -->
+* Module:
+  <!-- Please, include name(s) of relevant Tiller's module(s). If not related to any specific module, specify "project" instead. -->
+
+## Additional information
+
+<!-- Please, include any additional information that could be relevant (e.g. npm/yarn, OS version). -->
+
+## Feature description
+
+<!--
+  Please, describe the feature you envision.
+  For example, you might include (pseudo-)code snippets showing what it might look like.
+-->
+
+### Current behavior
+
+<!-- Please, provide the current behavior around this topic, if applicable. -->
+
+### Wanted behavior
+
+<!-- Please, describe the desired outcome around the suggested feature. -->
+
+### Possible workarounds
+
+<!-- Please, share any workarounds for the described feature, if applicable. -->

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: false

.github/pull_request_template.md

@@ -0,0 +1,65 @@
+<!--
+  Please use Markdown syntax throughout the report for improved clarity.
+  https://guides.github.com/features/mastering-markdown/
+-->
+
+## Basic information
+
+* Tiller version:
+  <!-- released version -->
+* Module:
+  <!-- Please, include name(s) of relevant Tiller's module(s). If not related to any specific module, specify "project" instead. -->
+
+## Additional information
+
+<!-- Please, include any additional information that could be relevant (e.g. npm/yarn, OS version). -->
+
+## Description
+
+### Summary
+
+<!--- Please, provide a short summary of your changes. -->
+
+### Details
+
+<!--- Please, describe your changes in detail. -->
+
+### Related issue
+
+<!--
+  If there is a related issue, please provide a reference to it.
+  If the related issue does not exist, please consider creating one.
+-->
+
+## Types of changes
+
+<!--- What types of changes does your code introduce? Please, remove all points that do not apply. -->
+
+- Bug fix (non-breaking change which fixes an issue)
+- Enhancement (non-breaking change which enhances existing functionality)
+- New feature (non-breaking change which adds functionality)
+- Breaking change (fix, enhancement or feature that would cause existing functionality to change in backward-incompatible way)
+- Docs change
+- Refactoring
+- Dependency upgrade
+
+## Checklist
+
+<!---
+  Please, go over all the following points, and put an "x" in all the boxes that apply.
+  If a point is out of scope (e.g. a change in build scripts is not required to be covered with tests),
+  please remove that box, strike through the sentence describing the point and add a short description
+  as to why that point is out of scope.
+  e.g.
+  - ~~I have added tests to cover my changes~~ (not needed as there are only changes to build files)
+-->
+
+- [ ] I have read the project's **CONTRIBUTING** document
+- [ ] I have checked my code with the project's static analysis tooling
+- [ ] I have formatted my code with the project's Prettier code-style configuration
+- [ ] I have checked my code for misspellings
+- [ ] I have organized my changes in easy-to-follow commits
+- [ ] My change requires a change to the documentation
+- [ ] I have updated the documentation accordingly
+- [ ] I have added a story to cover my changes
+- [ ] All new and existing story tests pass