Merge pull request #1 from LaswitchTech/dev

v0.0.0

Author: LouisOuellet

.editorconfig

@@ -0,0 +1,22 @@
+; http://editorconfig.org/
+
+root = true
+
+[*]
+indent_style = space
+indent_size = 4
+end_of_line = lf
+charset = utf-8
+trim_trailing_whitespace = true
+insert_final_newline = true
+
+[*.{yml,yaml}]
+indent_size = 2
+
+[{vendor,inc/phpseclib}/**]
+; Use editor default (possible autodetection).
+indent_style =
+indent_size =
+end_of_line =
+trim_trailing_whitespace =
+insert_final_newline =

.github/FUNDING.yml

@@ -0,0 +1,3 @@
+# These are supported funding model platforms
+
+github: [LaswitchTech]

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,31 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+### Description
+
+[Description of the bug or feature]
+
+### Steps to reproduce
+
+1. [First Step]
+2. [Second Step]
+3. [and so on...]
+
+**Expected behavior:** [What you expected to happen]
+
+**Actual behavior:** [What actually happened]
+
+### Versions
+
+* [PHP]
+* [Browser]
+
+### Screenshots or Logs
+
+[Paste your logs or attach the screenshot]

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: feature request
+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/pull_request_template.md

@@ -0,0 +1,55 @@
+## Description
+
+<!--
+Please provide a brief summary of the changes this PR introduces.
+Explain the problem being solved or the feature being added.
+-->
+
+## Related Issues
+
+<!--
+List related issues (e.g. "Fixes #123" or "Closes #456") to automatically link and close them
+when this PR is merged.
+-->
+
+## Proposed Changes
+
+<!--
+If relevant, list the main changes or highlight major improvements (e.g. "Added new API endpoint
+for user registration" or "Refactored the XYZ module for better performance").
+Provide enough context so reviewers can easily follow the changes.
+-->
+
+-
+-
+-
+
+## How Has This Been Tested?
+
+<!--
+Share details on how the changes have been tested (e.g., unit tests, manual testing,
+CI passes, etc.). If no tests were added or modified, explain why.
+-->
+
+## Screenshots (if appropriate)
+
+<!--
+If there's any UI change, attach screenshots or animated GIFs to illustrate it.
+-->
+
+## Checklist
+
+<!--
+Add any additional checks if needed.
+-->
+
+- [ ] My code follows the code style of this project
+- [ ] I have reviewed my changes for potential security vulnerabilities
+
+## Additional Comments
+
+<!--
+If you have any further comments or questions for the reviewers,
+mention them here. (e.g., concerns about certain aspects,
+ideas for further improvements, etc.)
+-->

.github/no-response.yml

@@ -0,0 +1,13 @@
+# Configuration for probot-no-response - https://github.com/probot/no-response
+
+# Number of days of inactivity before an Issue is closed for lack of response
+daysUntilClose: 14
+# Label requiring a response
+responseRequiredLabel: need more info
+# Comment to post when closing an Issue for lack of response. Set to `false` to disable
+closeComment: >
+  This issue has been automatically closed because there has been no response
+  to our request for more information from the original author. With only the
+  information that is currently in the issue, we don't have enough information
+  to take action. Please reach out if you have or find the answers we need so
+  that we can investigate further.

.github/workflows/release.yml

@@ -0,0 +1,81 @@
+name: Release
+
+on:
+  push:
+    tags:
+      - 'v*'
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v2
+        with:
+          fetch-depth: 0
+
+      - name: Set Tag as Filename
+        id: tag_name
+        run: echo "TAG_NAME=${GITHUB_REF##*/}" >> $GITHUB_ENV
+
+      - name: Create ZIP file
+        run: |
+          # -r : recurse
+          # -q : quiet (optional)
+          # -x : exclude patterns (globs)
+          zip -r "source.zip" . \
+            -x ".git/*" \
+            -x ".github/*" \
+            -x ".editorconfig" \
+            -x ".gitignore"
+
+      - name: Generate SHA256 checksum
+        run: sha256sum "source.zip" > "source.sha256"
+
+      - name: Generate Changelog
+        id: generate_changelog
+        run: |
+          # Find the most recent tag before the current one
+          PREV_TAG=$(git describe --tags --abbrev=0 HEAD^)
+
+          # Create a new CHANGELOG.md file with headers
+          echo -e "# Changelog\n" > CHANGELOG.md
+
+          # List commit messages between the previous tag and current HEAD
+          git log ${PREV_TAG}..HEAD --pretty=format:"* %s" >> CHANGELOG.md
+
+          # List unique contributors for these commits
+          echo -e "\n\n# Contributors\n" >> CHANGELOG.md
+          git log ${PREV_TAG}..HEAD --format='%aN' | sort -u | awk '{print "* " $0}' >> CHANGELOG.md
+
+      - name: Create Release
+        id: create_release
+        uses: actions/create-release@v1
+        env:
+          GITHUB_TOKEN: ${{ secrets.GH_PAT }}
+        with:
+          tag_name: ${{ github.ref }}
+          release_name: Release ${{ github.ref }}
+          draft: false
+          prerelease: false
+          body_path: ./CHANGELOG.md
+
+      - name: Upload Asset
+        uses: actions/upload-release-asset@v1
+        env:
+          GITHUB_TOKEN: ${{ secrets.GH_PAT }}
+        with:
+          upload_url: ${{ steps.create_release.outputs.upload_url }}
+          asset_path: ./source.zip
+          asset_name: source.zip
+          asset_content_type: application/zip
+
+      - name: Upload SHA256 Checksum
+        uses: actions/upload-release-asset@v1
+        env:
+          GITHUB_TOKEN: ${{ secrets.GH_PAT }}
+        with:
+          upload_url: ${{ steps.create_release.outputs.upload_url }}
+          asset_path: ./source.sha256
+          asset_name: source.sha256
+          asset_content_type: text/plain

.gitignore

@@ -0,0 +1,36 @@
+# Composer
+composer.phar
+*composer.phar
+.composer/
+/vendor/
+
+# Mac OS X
+.DS_Store
+*.DS_Store
+
+# Windows
+Thumbs.db
+Desktop.ini
+
+# Git
+.git
+TOKEN
+
+# Filetypes
+*.cfg
+*.log
+
+# Exclude Files
+!info.cfg
+!routes.cfg
+!styles.cfg
+!listing.cfg
+
+# Exclude Locales Configurations and Translations
+!Locale/*/*.cfg
+
+# Unique Directories
+/tmp/
+
+# Custom Module Files
+/Definition/

AUTHORS

@@ -0,0 +1 @@
+"LaswitchTech"<https://laswitchtech.com/>

CODE_OF_CONDUCT.md

@@ -0,0 +1,65 @@
+# Contributor Covenant Code of Conduct
+In order to foster a positive and inclusive community, we enforce a Code of Conduct in all of our projects and spaces. We expect all contributors, maintainers, and users to abide by its terms. Please read the full text so that you can understand what actions will and will not be tolerated.
+
+## 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 report@laswitchtech.com. 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](https://www.contributor-covenant.org), version 2.0, available at [https://www.contributor-covenant.org/version/2/0/code_of_conduct.html](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).