2026-05-13 14:13:57 +02:00
13 changed files with 441 additions and 7 deletions
@@ -0,0 +1,62 @@
+---
+name: 🐛 Bug Report
+about: Report a reproducible bug to help us improve the project
+title: "[bug]: "
+labels: bug
+assignees: ""
+---
+
+<!-- 🛑 **Please fill out the information below. Issues missing the required information will be automatically closed** 🛑 -->
+
+### Checklist
+
+- [ ] I have searched existing issues to ensure this bug hasn’t been reported yet.  
+- [ ] I have provided enough information for others to reproduce this bug.
+- [ ] I have encountered this issue at least twice
+- [ ] I have filled out all the information below
+
+> ⚠️ Please do not open an issue if you've encountered the undesired behavior only once.
+> Document your findings and include them in an issue when you can encounter the issue at least a second time
+
+## Description
+
+**Type**  
+
+- [ ] 💥 Crash  
+- [ ] ✖️ Build error  
+- [ ] 🫨 Instability  
+- [ ] 🤔 Other (please specify):
+
+**Encountered Behavior**  
+<!-- What happened? -->
+
+**Expected Behavior**  
+<!-- What should have happened instead? -->
+
+**Steps/Code Snippet to Reproduce**  
+<!-- Provide minimal, self-contained code or exact steps -->
+
+**Git Hash / Commit ID**  
+<!-- Paste the output of `git rev-parse HEAD` -->
+
+---
+
+## System Specs
+
+- **CPU** (model + architecture):  
+- **GPU** (model + driver version):
+- **Operating System & Version**:  
+- **Compiler / Build Tool Versions** (if relevant):  
+
+---
+
+## Additional Context
+
+**Logs / Error Output**  
+<!-- Paste error messages, stack traces, or build logs -->
+
+**Screenshots/Screencasts (if applicable)**  
+<!-- Add images or videos to help explain the problem -->
+
+**Workarounds Tried (optional)**  
+<!-- Any temporary fixes you found? -->
@@ -0,0 +1,65 @@
+---
+name: ✨ Feature Request
+about: Suggest a new feature or improvement for the project
+title: "[feature]: "
+labels: enhancement
+assignees: ""
+---
+
+<!-- 💡 **Please fill out the information below. Incomplete requests may be closed or moved to Discussions.** 💡 -->
+
+### Checklist
+
+- [ ] I have searched existing issues and discussions to ensure this feature hasn’t been suggested yet.  
+- [ ] I have clearly described the problem this feature would solve.  
+- [ ] I have outlined how this feature would improve the project for users or developers.  
+- [ ] I have filled out all the information below.
+
+## Summary
+
+**Feature Type**  
+
+- [ ] 🚀 End-user functionality  
+- [ ] 📦 Integration / New API  
+- [ ] 🎨 UI/UX improvement  
+- [ ] ⚡ Performance optimization  
+- [ ] 🧠 Developer experience improvement  
+- [ ] 🤔 Other (please specify):
+
+**Problem / Motivation**  
+<!-- What problem does this feature solve? Why is it needed? -->
+
+**Proposed Solution / Feature Description**  
+<!-- Describe your idea in detail. Include how it might work, appear, or behave. -->
+
+**Alternatives Considered**  
+<!-- What other approaches did you try or think about? Why aren’t they sufficient? -->
+
+---
+
+## Impact and Scope
+
+**Who Benefits**  
+<!-- Which users, teams, or use cases will this feature help? -->
+
+**Possible Risks or Tradeoffs**  
+<!-- Are there potential downsides, maintenance costs, or compatibility issues? -->
+
+**Priority Level**  
+
+- [ ] 💚 Nice-to-have  
+- [ ] 💖 Important  
+- [ ] 🔥 Critical / Blocking  
+
+---
+
+## Additional Context
+
+**Related Issues / PRs**  
+<!-- Link to related issues or pull requests if any -->
+
+**Mockups / Diagrams / Examples (optional)**  
+<!-- Add visuals, sketches, or example code to clarify your idea -->
+
+**Notes or References (optional)**  
+<!-- Links, research, or external references that support your proposal -->
@@ -0,0 +1,70 @@
+---
+name: 😓 QA Issue
+about: Report a QA issue you've encountered
+title: "[qa]: "
+labels: qa
+assignees: ""
+---
+
+<!-- 🛑 **Please fill out the information below. Issues missing the required information will be automatically closed** 🛑 -->
+
+### Checklist
+
+- [ ] I have searched existing issues to ensure this hasn’t been reported yet.  
+- [ ] I have provided enough information for others to identify the issue.
+- [ ] I have encountered this issue at least twice
+- [ ] I have filled out all the information below
+
+> ⚠️ Please do not open an issue if you've encountered the undesired behavior only once.
+> Document your findings and include them in an issue when you can encounter the issue at least a second time
+
+## Description
+
+**Type**  
+
+- [ ] 🔍 Analyzer/Lint/Tidy
+- [ ] 📏 Formatting
+- [ ] 🎨 Code style
+- [ ] 🛠️ Build issue
+- [ ] 📚 Documentation
+- [ ] 🧪 Test failure/coverage
+- [ ] 🔄 CI/CD
+- [ ] ⚡ Performance (CPU/GPU/Memory usage, latency, etc.)
+- [ ] 📦 Installation/Setup
+- [ ] 🔌 API
+- [ ] 🤔 Other (please specify):
+
+**Encountered Behavior**  
+<!-- What happened? -->
+
+**Expected Behavior**  
+<!-- What should have happened instead? -->
+
+**Steps/Code Snippet to Reproduce**  
+<!-- Provide minimal, self-contained code or exact steps -->
+
+**Version tag / Git commit**  
+<!-- Paste the output of `git rev-parse HEAD` -->
+
+---
+
+## System Specs (if applicable)
+<!-- If not applicable, delete the list below and write "N/A" -->
+
+- **CPU** (model + architecture):  
+- **GPU** (model + driver version):
+- **Operating System & Version**:  
+- **Compiler / Build Tool Versions** (if relevant):  
+
+---
+
+## Additional Context
+
+**Logs / Error Output**  
+<!-- Paste error messages, stack traces, or build logs -->
+
+**Screenshots/Screencasts (if applicable)**  
+<!-- Add images or videos to help explain the problem -->
+
+**Workarounds Tried (optional)**  
+<!-- Any temporary fixes you found? -->
@@ -0,0 +1,27 @@
+<!--
+  Thanks for contributing! 🩵
+    Please make sure to follow the contribution guidelines outlined in our [CONTRIBUTING.md](CONTRIBUTING.md) file, and adhere to our [Code of Conduct](CODE_OF_CONDUCT.md) to maintain a welcoming and inclusive community for everyone.
+
+    When submitting a pull request, please provide a clear description of your changes, and select the appropriate type of change from the checklist below ✨
+
+    This helps us review and merge your contribution more efficiently 🫶
+-->
+
+<!-- 🛑 **Please fill out the information below. Issues missing the required information will be automatically closed** 🛑 -->
+
+## Related issue(s)
+<!-- Link to any related issues or pull requests here -->
+
+## Type of Change
+<!--- Put an `x` in all the boxes that apply: -->
+
+- [ ] ✨ Feature (new API/UI/functionality)
+- [ ] 🐛 Bug fix (fixes an issue)
+- [ ] ❌ Breaking change (a change that would cause existing functionality to work differently or break)
+- [ ] 🧹 Code refactor
+- [ ] ✅ CI/CD/Build configuration change
+- [ ] 📚 Documentation
+- [ ] 🧹 Chore
+
+## Description
+<!--- Describe your changes in detail -->
@@ -1,7 +1,38 @@
-# https://dart.dev/guides/libraries/private-files
-# Created by `dart pub`
-.dart_tool/
+# See https://www.dartlang.org/guides/libraries/private-files

-# Avoid committing pubspec.lock for library packages; see
-# https://dart.dev/guides/libraries/private-files#pubspeclock.
+# Files and directories created by pub
+.dart_tool/
+.packages
+# If you're building an application, you may want to check-in your pubspec.lock
 pubspec.lock
+*.g.dart
+
+# Directory created by dartdoc
+# If you don't generate documentation locally you can remove this line.
+doc/api/
+
+# dotenv environment variables file
+.env*
+
+# Build files
+build/
+.idea/
+*.iml
+
+# Avoid committing generated Javascript files:
+*.dart.js
+# Produced by the --dump-info flag.
+*.info.json
+# When generated by dart2js. Don't specify *.js if your
+# project includes source files written in JavaScript.
+*.js
+*.js_
+*.js.deps
+*.js.map
+
+.flutter-plugins
+.flutter-plugins-dependencies
+
+# OS generated files
+.DS_Store
+Thumbs.db
@@ -0,0 +1,5 @@
+.github/
+.dart_tool/
+build/
+*.g.dart
+screenshots/
@@ -1,3 +1,7 @@
 ## 1.0.0

+- `toString` no longer tries `firstOrNull` as it should never return null.
+
+## 1.0.0
+
 - Initial version.
@@ -0,0 +1,86 @@
+
+# Contributor Covenant 3.0 Code of Conduct
+
+## Our Pledge
+
+We pledge to make our community welcoming, safe, and equitable for all.
+
+We are committed to fostering an environment that respects and promotes the dignity, rights, and contributions of all individuals, regardless of characteristics including race, ethnicity, caste, color, age, physical characteristics, neurodiversity, disability, sex or gender, gender identity or expression, sexual orientation, language, philosophy or religion, national or social origin, socio-economic position, level of education, or other status. The same privileges of participation are extended to everyone who participates in good faith and in accordance with this Covenant.
+
+## Encouraged Behaviors
+
+While acknowledging differences in social norms, we all strive to meet our community's expectations for positive behavior. We also understand that our words and actions may be interpreted differently than we intend based on culture, background, or native language.
+
+With these considerations in mind, we agree to behave mindfully toward each other and act in ways that center our shared values, including:
+
+1. Respecting the **purpose of our community**, our activities, and our ways of gathering.
+2. Engaging **kindly and honestly** with others.
+3. Respecting **different viewpoints** and experiences.
+4. **Taking responsibility** for our actions and contributions.
+5. Gracefully giving and accepting **constructive feedback**.
+6. Committing to **repairing harm** when it occurs.
+7. Behaving in other ways that promote and sustain the **well-being of our community**.
+
+## Restricted Behaviors
+
+We agree to restrict the following behaviors in our community. Instances, threats, and promotion of these behaviors are violations of this Code of Conduct.
+
+1. **Harassment.** Violating explicitly expressed boundaries or engaging in unnecessary personal attention after any clear request to stop.
+2. **Character attacks.** Making insulting, demeaning, or pejorative comments directed at a community member or group of people.
+3. **Stereotyping or discrimination.** Characterizing anyone’s personality or behavior on the basis of immutable identities or traits.
+4. **Sexualization.** Behaving in a way that would generally be considered inappropriately intimate in the context or purpose of the community.
+5. **Violating confidentiality**. Sharing or acting on someone's personal or private information without their permission.
+6. **Endangerment.** Causing, encouraging, or threatening violence or other harm toward any person or group.
+7. Behaving in other ways that **threaten the well-being** of our community.
+
+### Other Restrictions
+
+1. **Misleading identity.** Impersonating someone else for any reason, or pretending to be someone else to evade enforcement actions.
+2. **Failing to credit sources.** Not properly crediting the sources of content you contribute.
+3. **Promotional materials**. Sharing marketing or other commercial content in a way that is outside the norms of the community.
+4. **Irresponsible communication.** Failing to responsibly present content which includes, links or describes any other restricted behaviors.
+
+## Reporting an Issue
+
+Tensions can occur between community members even when they are trying their best to collaborate. Not every conflict represents a code of conduct violation, and this Code of Conduct reinforces encouraged behaviors and norms that can help avoid conflicts and minimize harm.
+
+When an incident does occur, it is important to report it promptly. To report a possible violation, **contact the maintainers via their social media accounts or email address, as listed on their profile**
+
+Community Moderators take reports of violations seriously and will make every effort to respond in a timely manner. They will investigate all reports of code of conduct violations, reviewing messages, logs, and recordings, or interviewing witnesses and other participants. Community Moderators will keep investigation and enforcement actions as transparent as possible while prioritizing safety and confidentiality. In order to honor these values, enforcement actions are carried out in private with the involved parties, but communicating to the whole community may be part of a mutually agreed upon resolution.
+
+## Addressing and Repairing Harm
+
+**[NOTE: The remedies and repairs outlined below are suggestions based on best practices in code of conduct enforcement. If your community has its own established enforcement process, be sure to edit this section to describe your own policies.]**
+
+If an investigation by the Community Moderators finds that this Code of Conduct has been violated, the following enforcement ladder may be used to determine how best to repair harm, based on the incident's impact on the individuals involved and the community as a whole. Depending on the severity of a violation, lower rungs on the ladder may be skipped.
+
+1) Warning
+   1) Event: A violation involving a single incident or series of incidents.
+   2) Consequence: A private, written warning from the Community Moderators.
+   3) Repair: Examples of repair include a private written apology, acknowledgement of responsibility, and seeking clarification on expectations.
+2) Temporarily Limited Activities
+   1) Event: A repeated incidence of a violation that previously resulted in a warning, or the first incidence of a more serious violation.
+   2) Consequence: A private, written warning with a time-limited cooldown period designed to underscore the seriousness of the situation and give the community members involved time to process the incident. The cooldown period may be limited to particular communication channels or interactions with particular community members.
+   3) Repair: Examples of repair may include making an apology, using the cooldown period to reflect on actions and impact, and being thoughtful about re-entering community spaces after the period is over.
+3) Temporary Suspension
+   1) Event: A pattern of repeated violation which the Community Moderators have tried to address with warnings, or a single serious violation.
+   2) Consequence: A private written warning with conditions for return from suspension. In general, temporary suspensions give the person being suspended time to reflect upon their behavior and possible corrective actions.
+   3) Repair: Examples of repair include respecting the spirit of the suspension, meeting the specified conditions for return, and being thoughtful about how to reintegrate with the community when the suspension is lifted.
+4) Permanent Ban
+   1) Event: A pattern of repeated code of conduct violations that other steps on the ladder have failed to resolve, or a violation so serious that the Community Moderators determine there is no way to keep the community safe with this person as a member.
+   2) Consequence: Access to all community spaces, tools, and communication channels is removed. In general, permanent bans should be rarely used, should have strong reasoning behind them, and should only be resorted to if working through other remedies has failed to change the behavior.
+   3) Repair: There is no possible repair in cases of this severity.
+
+This enforcement ladder is intended as a guideline. It does not limit the ability of Community Managers to use their discretion and judgment, in keeping with the best interests of our community.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public or other spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Attribution
+
+This Code of Conduct is adapted from the Contributor Covenant, version 3.0, permanently available at [https://www.contributor-covenant.org/version/3/0/](https://www.contributor-covenant.org/version/3/0/).
+
+Contributor Covenant is stewarded by the Organization for Ethical Source and licensed under CC BY-SA 4.0. To view a copy of this license, visit [https://creativecommons.org/licenses/by-sa/4.0/](https://creativecommons.org/licenses/by-sa/4.0/)
+
+For answers to common questions about Contributor Covenant, see the FAQ at [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). Translations are provided at [https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations). Additional enforcement and community guideline resources can be found at [https://www.contributor-covenant.org/resources](https://www.contributor-covenant.org/resources). The enforcement ladder was inspired by the work of [Mozilla’s code of conduct team](https://github.com/mozilla/inclusion).
@@ -0,0 +1,81 @@
+# Contributing
+
+Thanks for taking the time to contribute — you’re helping make the Dart ecosystem better.
+
+By participating in this project, you agree to follow our [Code of Conduct](CODE_OF_CONDUCT.md).
+
+## Ways to contribute
+
+- Report bugs
+- Suggest enhancements
+- Improve documentation
+- Submit pull requests
+- Share examples and use-cases
+
+## Questions and discussions
+
+If you’re unsure whether something is a bug or a feature request, open an issue and describe:
+
+- What you expected to happen
+- What actually happened
+- Steps to reproduce (if applicable)
+- Your Dart SDK version (`dart --version`)
+
+## Filing issues
+
+When opening an issue, please include:
+
+- A clear title and description
+- Reproduction steps (minimal, if possible)
+- Expected vs actual behavior
+- Logs, stack traces, or screenshots (if relevant)
+
+## Development setup
+
+Prerequisites:
+
+- Dart SDK (see `pubspec.yaml` for the supported SDK range)
+
+Common commands:
+
+- Get dependencies: `dart pub get`
+- Format: `dart format .`
+- Analyze: `dart analyze`
+- Run tests: `dart test`
+
+Tip: Keep your editor set to “format on save”.
+
+## Pull requests
+
+We welcome PRs of all sizes. Small, focused PRs are easiest to review.
+
+### Before you submit
+
+- Run `dart format .`
+- Run `dart analyze`
+- Run `dart test`
+- Update documentation if behavior or APIs changed
+- Add or update tests for bug fixes and new features
+- If you changed public API, update `CHANGELOG.md`
+
+### PR scope guidelines
+
+- Keep PRs focused on a single concern (feature, fix, docs)
+- Avoid drive-by refactors unless they’re necessary for the change
+- Prefer backwards-compatible improvements when possible
+
+### Review process
+
+Maintainers will aim to respond, but response time can vary. If you haven’t heard back after a reasonable amount of time, a gentle ping is welcome.
+
+## Security
+
+If you discover a security issue, please **do not** open a public issue.
+
+Instead, report it privately to the maintainer(s)!
+
+## Licensing of contributions
+
+Unless stated otherwise, contributions you submit are provided under this project’s license (see [LICENSE](LICENSE)).
+
+If your organization requires a Contributor License Agreement (CLA) or similar, replace this section with your preferred process.
@@ -111,7 +111,7 @@ class ListOr<T> extends Object with ListMixin<T> {
  @override
  String toString() {
    if (_items.length == 1) {
-      return _items.firstOrNull.toString();
+      return _items.first.toString();
    }
    return _items.toString();
  }
@@ -1,6 +1,9 @@
 name: list_or
 description: A Dart utility that seamlessly normalizes single values and iterables into a unified, type-safe List.
-version: 1.0.0
+version: 1.0.1
+
+license: BSD 3-Clause License
+homepage: https://git.hadak.org/dart/list_or
 repository: https://git.hadak.org/dart/list_or
 issue_tracker: https://git.hadak.org/dart/list_or/issues