chore: new generator output

[Brazol]

Summary by CodeRabbit

• Chores
  • Updated analyzer configuration across multiple project locations to exclude the build/ directory from lint analysis.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 9058cef1-89ba-430e-bb31-d112a9c8400e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

📝 Walkthrough

Walkthrough

Three analysis_options.yaml files (root, docs/, and packages/stream_feeds/example/) are each updated to add build/** to the Dart analyzer exclude list, preventing lint analysis from running on generated build artifacts.

Changes

Analyzer Exclude Config Update

Layer / File(s)	Summary
Add build/** exclusion to all analysis configs analysis_options.yaml, docs/analysis_options.yaml, packages/stream_feeds/example/analysis_options.yaml	Adds build/** to the analyzer.exclude list in all three config files so generated build artifacts are skipped during lint analysis.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐇 Hoppy news from the warren today,
Build folders are now swept out of the way!
No linting on artifacts, no warnings in store,
Three config files tidied — who could ask for more?
✨ The meadow is cleaner, the burrow is bright!

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	No pull request description was provided; the required template sections including CLA, description, and testing information are completely missing.	Add a complete pull request description following the template, including CLA checkbox, description of changes, and testing information. At minimum, explain why the build/** directory exclusion was added to analysis_options.yaml files.
Title check	❓ Inconclusive	The title 'chore: new generator output' is vague and does not clearly communicate the specific changes made to the codebase.	Use a more descriptive title that specifies what was updated, such as 'chore: exclude build directory from analyzer configuration' to better convey the actual changes.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/new-generator-code

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}