Initial commit

.editorconfig

@@ -0,0 +1,14 @@
+root = true
+
+[*]
+indent_size = 2
+max_line_length = 100
+indent_style = space
+insert_final_newline = true
+trim_trailing_whitespace = true
+ij_kotlin_allow_trailing_comma = true
+ij_kotlin_allow_trailing_comma_on_call_site = true
+
+[*.{kt, kts}]
+ktlint_standard_filename = disabled
+ktlint_standard_max-line-length = disabled

.github/CODEOWNERS

@@ -0,0 +1,16 @@
+# Lines starting with '#' are comments.
+# Each line is a file pattern followed by one or more owners.
+
+# More details are here: https://help.github.com/articles/about-codeowners/
+
+# The '*' pattern is global owners.
+# Not adding in this PR, but I'd like to try adding a global owner set with the entire team.
+# One interpretation of their docs is that global owners are added only if not removed
+# by a more local rule.
+
+# Order is important. The last matching pattern has the most precedence.
+# The folders are ordered as follows:
+
+# In each subsection folders are ordered first by depth, then alphabetically.
+# This should make it easy to add new rules without breaking existing ones.
+*       @teogor

.github/FUNDING.yml

@@ -0,0 +1,13 @@
+# These are supported funding model platforms
+
+github: [ teogor ]
+patreon: # Replace with a single Patreon username
+open_collective: # Replace with a single Open Collective username
+ko_fi: # Replace with a single Ko-fi username
+tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
+community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
+liberapay: # Replace with a single Liberapay username
+issuehunt: # Replace with a single IssueHunt username
+otechie: # Replace with a single Otechie username
+lfx_crowdfunding: # Replace with a single LFX Crowdfunding project-name e.g., cloud-foundry
+custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']

.github/ISSUE_TEMPLATE/Bug_report.md

@@ -0,0 +1,17 @@
+---
+name: Bug report about: Something is crashing or not working as intended
+
+---
+
+**Please complete the following information:**
+
+- Library Version [e.g. v1.0.0]
+- Affected Device(s) [e.g. Samsung Galaxy S22 Ultra with Android 12.0]
+
+**Describe the Bug:**
+
+Add a clear description about the problem.
+
+**Expected Behavior:**
+
+A clear description of what you expected to happen.

.github/ISSUE_TEMPLATE/Feature_request.md

@@ -0,0 +1,16 @@
+---
+name: Feature request about: Suggest an idea for this project
+
+---
+
+**Is your feature request related to a problem?**
+
+A clear and concise description of what the problem is.
+
+**Describe the solution you'd like:**
+
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered:**
+
+A clear description of any alternative solutions you've considered.

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,46 @@
+name: Bug Report
+description: File a bug report
+title: "[Bug]: "
+labels: [ "bug", "triage me" ]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report!
+  - type: checkboxes
+    attributes:
+      label: Is there an existing issue for this?
+      description: Please search to see if an issue already exists for the bug you encountered.
+      options:
+        - label: I have searched the existing issues
+          required: true
+  - type: checkboxes
+    attributes:
+      label: Is there a StackOverflow question about this issue?
+      description: Please search [StackOverflow](https://stackoverflow.com/questions/tagged/gleam) if an issue with an answer already exists for the bug you encountered.
+      options:
+        - label: I have searched StackOverflow
+          required: true
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened?
+      description: Also tell us, what did you expect to happen?
+      placeholder: Tell us what you see!
+      value: "A bug happened!"
+    validations:
+      required: true
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant logcat output
+      description: Please copy and paste any relevant logcat output. This will be automatically formatted into code, so no need for backticks.
+      render: shell
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: By submitting this issue, you agree to follow our [Code of Conduct](CODE_OF_CONDUCT.md)
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true

.github/ISSUE_TEMPLATE/docs_issue.yml

@@ -0,0 +1,38 @@
+name: Documentation issue
+description: File an issue or make a suggestion for the project documentation
+title: "[Documentation]: "
+labels: [ "documentation" ]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to improve our documentation!
+  - type: checkboxes
+    attributes:
+      label: Is there an existing issue for this?
+      description: Please search to see if an issue already exists for the documentation issue you encountered.
+      options:
+        - label: I have searched the existing issues
+          required: true
+  - type: input
+    id: page-url
+    attributes:
+      label: Page URL (type "NEW" for a new page suggestion)
+    validations:
+      required: true
+  - type: textarea
+    id: what-needs-improving
+    attributes:
+      label: What's the documentation problem or suggestion?
+      placeholder: Tell us what should be improved!
+      value: "Docs need improving!"
+    validations:
+      required: true
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: By submitting this issue, you agree to follow our [Code of Conduct](CODE_OF_CONDUCT.md)
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,46 @@
+name: Feature request
+description: File a feature request
+title: "[FR]: "
+labels: [ "enhancement", "triage me" ]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report!
+  - type: checkboxes
+    attributes:
+      label: Is there an existing issue for this?
+      description: Please search to see if an issue already exists for this feature request.
+      options:
+        - label: I have searched the existing issues
+          required: true
+  - type: textarea
+    id: describe-problem
+    attributes:
+      label: Describe the problem
+      description: Is your feature request related to a problem? Please describe.
+      placeholder: I'm always frustrated when...
+    validations:
+      required: true
+  - type: textarea
+    id: solution
+    attributes:
+      label: Describe the solution
+      description: Please describe the solution you'd like. A clear and concise description of what you want to happen.
+    validations:
+      required: true
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional context
+      description: Add any other context or screenshots about the feature request here.
+    validations:
+      required: false
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: By submitting this issue, you agree to follow our [Code of Conduct](CODE_OF_CONDUCT.md)
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true

.github/PULL_REQUEST_TEMPLATE/pull_request_template.md

@@ -0,0 +1,21 @@
+---
+name: Pull request
+about: Create a pull request
+label: 'triage me'
+---
+Thank you for opening a Pull Request!
+Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
+
+- [ ] Make sure to open a GitHub issue as a bug/feature request before writing your code! That way
+  we can discuss the change, evaluate designs, and agree on the general idea
+- [ ] Ensure the tests and linter
+  pass (`./gradlew --init-script gradle/init.gradle.kts spotlessApply` to automatically apply
+  formatting)
+- [ ] Appropriate docs were updated (if necessary)
+
+Is this your first Pull Request?
+
+- [ ] Run `./tools/setup.sh`
+- [ ] Import the code formatting style as explained in [the setup script](/tools/setup.sh#L40).
+
+Fixes #<issue_number_goes_here> 🍃

.github/ci-gradle.properties

@@ -0,0 +1,28 @@
+#
+# Copyright 2024 teogor (Teodor Grigor)
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#      http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+#
+
+org.gradle.daemon=false
+org.gradle.parallel=true
+org.gradle.workers.max=2
+
+kotlin.incremental=false
+kotlin.compiler.execution.strategy=in-process
+
+# Controls KotlinOptions.allWarningsAsErrors.
+# This value used in CI and is currently set to false.
+# If you want to treat warnings as errors locally, set this property to true
+# in your ~/.gradle/gradle.properties file.
+warningsAsErrors=false

.github/pull_request_template.md

@@ -0,0 +1,23 @@
+## Guidelines
+
+Describe the big picture of your changes here to communicate to the maintainers why we should accept
+this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.
+
+### Types of changes
+
+What types of changes does your code introduce?
+
+- [ ] Bugfix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as
+  expected)
+
+### Preparing a pull request for review
+
+Ensure your change is properly formatted by running:
+
+```gradle
+$ ./gradlew spotlessApply
+```
+
+Please correct any failures before requesting a review.