First Commit

.fleet/run.json

@@ -0,0 +1,17 @@
+{
+    "configurations": [
+        {
+            "name": "Run Bash",
+            "program": "/usr/bin/bash",
+            "type": "command"
+        },
+        {
+            "args": [
+                "build"
+            ],
+            "name": "Dart Compile",
+            "program": "/usr/bin/dart-sdk/bin",
+            "type": "command"
+        }
+    ]
+}

.fleet/settings.json

@@ -0,0 +1 @@
+{}

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+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.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* 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
+
+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
+.
+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 community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

.github/CONTRIBUTING.md

@@ -0,0 +1,44 @@
+[Guide]: https://opensource.guide/
+
+<a href="https://github.com/github/opensource.guide">
+  <h1>
+    <picture>
+      <img src="https://github.com/github/opensource.guide/blob/main/assets/images/cards/contribute.png" alt="">
+    </picture>
+  </h1>
+</a>
+
+# Contributing
+
+Give context. Help others get quickly up to speed. If you’re running into an error, explain what you’re trying to do and
+how to reproduce it. If you’re suggesting a new idea, explain why you think it’d be useful to the project.
+
+Do your homework beforehand. It’s OK not to know things, but show that you tried. Before asking for help, be sure to
+check a project’s README, documentation, issues, mailing list, and search the internet for an answer. People will
+appreciate it when you demonstrate that you’re trying to learn.
+
+Keep requests short and direct. Much like sending an email, every contribution, no matter how simple or helpful,
+requires someone else’s review. Many projects have more incoming requests than people available to help. Be concise. You
+will increase the chance that someone will be able to help you.
+
+Keep all communication public. Although it’s tempting, don’t reach out to maintainers privately unless you need to share
+sensitive information. When you keep the conversation public, more people can learn and benefit from your exchange.
+Discussions can be, in themselves, contributions.
+
+It’s okay to ask questions. Everybody was new to the project at some point, and even experienced contributors need to
+get up to speed when they look at a new project. By the same token, even longtime maintainers are not always familiar
+with every part of the project. Show them the same patience that you’d want them to show to you.
+
+Respect community decisions. Your ideas may differ from the community’s priorities or vision. They may offer feedback or
+decide not to pursue your idea. While you should discuss and look for compromise, maintainers have to live with your
+decision longer than you will. If you disagree with their direction, you can always work on your own fork or start your
+own project.
+
+Above all, keep it classy. Open source is made up of collaborators from all over the world. Context gets lost across
+languages, cultures, geographies, and time zones. In addition, written communication makes it harder to convey a tone or
+mood. Assume good intentions in these conversations. It’s fine to politely push back on an idea, ask for more context,
+or further clarify your position. Just try to leave the internet a better place than when you found it.
+
+## Attribution
+
+This Contributing Template is adapted from the [GitHub Open Source Guide][Guide]

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,38 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+ - OS: [e.g. iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+
+**Smartphone (please complete the following information):**
+ - Device: [e.g. iPhone6]
+ - OS: [e.g. iOS8.1]
+ - Browser [e.g. stock browser, safari]
+ - Version [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,33 @@
+[Guide]: https://opensource.guide/
+
+<a href="https://github.com/github/opensource.guide">
+  <h1>
+    <picture>
+      <img src="https://github.com/github/opensource.guide/blob/main/assets/images/cards/best-practices.png" alt="">
+    </picture>
+  </h1>
+</a>
+
+# Pull Request Template
+
+● Fork the repository and clone it locally. Connect your local to the original upstream repository by adding it as a
+remote. Pull in changes from upstream often so that you stay up to date so that when you submit your pull request, merge
+conflicts will be less likely.
+
+● Create a branch for your edits.
+
+● Reference any relevant issues or supporting documentation in your PR
+
+● Include screenshots of the before and after if your changes include differences in HTML/CSS. Drag and drop the images
+into the body of your pull request.
+
+● Test your changes. Run your changes against any existing tests if they exist and create new ones when needed. Whether
+tests exist or not, make sure your changes don’t break the existing project.
+
+● Contribute in the style of the project to the best of your abilities. This may mean using indents, semi-colons or
+comments differently than you would in your own repository, but makes it easier for the maintainer to merge, others to
+understand and maintain in the future.
+
+## Attribution
+
+This Pull Request Template is adapted from the [GitHub Open Source Guide][Guide]

.github/SECURITY.md

@@ -0,0 +1,15 @@
+[Report]: https://github.com/HyaenaTechnologies/calculate_engine_web/security/advisories
+
+# Security Policy
+
+## Supported Versions
+
+| Version | Support     |
+|---------|-------------|
+| > 0.2.0 | Supported   |
+| = 0.2.0 | Supported   |
+| < 0.2.0 | Unsupported |
+
+## Reporting a Vulnerability
+
+[Report Vulnerability][Report]

.github/dependabot.yml

@@ -0,0 +1,20 @@
+updates:
+  - package-ecosystem: "github-actions"
+    commit-message:
+      prefix: "Actions"
+    directory: "/" 
+    schedule:
+      day: "saturday"
+      interval: "weekly"
+      time: "03:00"
+
+  - package-ecosystem: "pub"
+    commit-message:
+      prefix: "Pub"
+    directory: "/" 
+    schedule:
+      day: "saturday"
+      interval: "weekly"
+      time: "03:00"
+
+version: 2

.github/workflows/dart.yml

@@ -0,0 +1,43 @@
+name: Dart
+
+on:
+  push:
+    branches: [ "main" ]
+
+  pull_request:
+    branches: [ "main" ]
+
+  schedule:
+  - cron: "30 03 * * 6"
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+
+    - name: Checkout Repository
+      uses: actions/[email protected]
+
+    - name: Set up Dart
+      uses: dart-lang/[email protected]
+
+    - name: Analyze Package
+      run: dart analyze lib
+
+    - name: Environment Information
+      run: dart info 
+
+    - name: Fix Package Dry Run 
+      run: dart fix lib --dry-run
+
+    - name: Fix Package Apply
+      run: dart fix lib --apply
+
+    - name: Format Package 
+      run: dart format lib
+
+    - name: Dependency Graph
+      run: dart pub deps
+
+    - name: Upgrade Packages
+      run: dart pub upgrade