First commit

Author: proninyaroslav

.github/pull_request_template.md

@@ -0,0 +1,8 @@
+*Replace this paragraph with a description of what this PR is changing or adding, and why. Consider including before/after screenshots.*
+
+## Pre-launch Checklist
+
+- [ ] I read the [Contributor Guide](CONTRIBUTING.md) and followed the process outlined there for submitting PRs.
+- If you made changes to the code:
+  - [ ] I added new tests to check the change I am making or feature I am adding.
+  - [ ] All existing and new tests are passing.

.github/workflows/flutter_test.yml

@@ -0,0 +1,22 @@
+name: Flutter Test CI
+
+on: [push, pull_request]
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v2
+    - uses: subosito/flutter-action@v1.4.0
+      with:
+        flutter-version: '2.2.x'
+    - name: Disable Google Analytics
+      run: flutter config --no-analytics
+    - name: Install dependencies
+      run: flutter pub get
+    - name: Analyze code
+      run: flutter analyze
+    - name: Run tests
+      run: flutter test test

.gitignore

@@ -0,0 +1,47 @@
+# Miscellaneous
+*.class
+*.log
+*.pyc
+*.swp
+.DS_Store
+.atom/
+.buildlog/
+.history
+.svn/
+
+# IntelliJ related
+*.iml
+*.ipr
+*.iws
+.idea/
+
+# The .vscode folder contains launch configuration and tasks you configure in
+# VS Code which you may wish to be included in version control, so this line
+# is commented out by default.
+#.vscode/
+
+# Flutter/Dart/Pub related
+**/doc/api/
+.dart_tool/
+.flutter-plugins
+.flutter-plugins-dependencies
+.packages
+.pub-cache/
+.pub/
+/build/
+
+# Web related
+lib/generated_plugin_registrant.dart
+
+# Symbolication related
+app.*.symbols
+
+# Obfuscation related
+app.*.map.json
+
+# Exceptions to above rules.
+!/packages/flutter_tools/test/data/dart_dependencies_test/**/.packages
+
+# Envinronment
+.env
+.env_test

.metadata

@@ -0,0 +1,10 @@
+# This file tracks properties of this Flutter project.
+# Used by Flutter tool to assess capabilities and perform upgrades etc.
+#
+# This file should be version controlled and should not be manually edited.
+
+version:
+  revision: 1ad9baa8b99a2897c20f9e6e54d3b9b359ade314
+  channel: stable
+
+project_type: app

.vscode/launch.json

@@ -0,0 +1,40 @@
+{
+    // Use IntelliSense to learn about possible attributes.
+    // Hover to view descriptions of existing attributes.
+    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
+    "version": "0.2.0",
+    "configurations": [
+        {
+            "name": "Flutter Debug",
+            "request": "launch",
+            "type": "dart",
+            "flutterMode": "debug",
+            "args": ["--flavor", "main"],
+        },
+        {
+            "name": "Flutter Release",
+            "request": "launch",
+            "type": "dart",
+            "flutterMode": "release",
+            "args": ["--flavor", "main"]
+        },
+        {
+            "name": "Flutter Profile",
+            "request": "launch",
+            "type": "dart",
+            "flutterMode": "profile",
+            "args": ["--flavor", "main"]
+        },
+        {
+            "name": "Flutter: Attach to Device",
+            "type": "dart",
+            "request": "attach"
+        },
+        {
+            "name": "Flutter: Run all Tests",
+            "type": "dart",
+            "request": "launch",
+            "program": "./test/"
+        },
+    ],
+}

CONTRIBUTING.md

@@ -0,0 +1,57 @@
+Contributor Guide
+=====================
+
+## 🌍 Note for translators
+
+Localization files are located in the [lib/l10n](lib/l10n) directory.
+
+The app uses ARB format for localization. If you wonder how to format key-values content inside ARB files, [here](https://github.com/google/app-resource-bundle/wiki/ApplicationResourceBundleSpecification) is detailed explanation.
+
+If you are making changes to the localization files, run the following command:
+```
+flutter pub run intl_utils:generate
+```
+
+If you added a new language, make sure to add it to the [lib/locale.dart](lib/locale.dart).
+
+Detailed documentation on `intl_utils` [here](https://pub.dev/packages/intl_utils).
+
+## ⚙️ How to make changes in the code
+
+### 1. Where to begin
+
+Start by looking at the [open issues](https://github.com/proninyaroslav/libretrack/issues) to contribute code.
+
+Make sure to write your name and e-mail address in format `Name <e-mail>` in the license declaration above every file you make changes to.
+
+Repeat and rinse, if you send enough patches to demonstrate you have a good coding skills, you will be given commit access on the real repo, making you part of the development team.
+
+Also, take a look at [**Coding Guidelines**](#-coding-guidelines) before making code changes.
+
+### 2. After making changes
+
+Be sure to run `build_runner` before creating your commit:
+```
+flutter pub run build_runner build --delete-conflicting-outputs
+```
+
+Detailed documentation on `build_runner` [here](https://pub.dev/packages/build_runner).
+
+If you are making changes to the localization files, also read the [Note for translators](#-note-for-translators) section.
+
+### 3. Testing
+
+Make sure that all existing and new tests are passing:
+```
+flutter test test
+```
+
+## 📋 Coding Guidelines
+
+ - Keep it snimple snupid: [KISS](https://en.wikipedia.org/wiki/KISS_principle)
+ - No repeating yourself. [Re-use your own code and that of others](https://en.wikipedia.org/wiki/Don%27t_repeat_yourself).
+ - If you want to help, triaging and keeping up with the issue and TODO list is great.
+ - Try to follow our coding style and formatting before submitting a patch.
+ - All merge requests should come from a feature branch created on your Git fork. Your code will be reviewed, and only merged to the master branch if it doesn't break the build.
+ - When you submit a merge request, try to explain what issue you're fixing, and what you're fixing in detail, so it's easier for us to read your patches.
+ - Well named methods and code re-usability is preferable to a lot of comments.