chore: bump analyzer version to 13.0.0 and refactor default expression method

[AngeloAvv]

No description provided.

[coderabbitai]

Warning

Review limit reached

@AngeloAvv, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 54 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 768933cb-4d86-41f7-8874-90e2246fc795

📥 Commits

Reviewing files that changed from the base of the PR and between 1447ef2 and 8fba37f.

📒 Files selected for processing (1)

• packages/dart_mapper_generator/pubspec.yaml

📝 Walkthrough

Walkthrough

A local helper function in default_expression_factory.dart was renamed from _buildDefaultExpr to buildDefaultExpr, with its call site updated accordingly. Separately, the analyzer dependency constraint in pubspec.yaml was bumped from ^12.0.0 to ^13.0.0.

Changes

Helper Rename and Dependency Update

Layer / File(s)	Summary
Default expression helper rename packages/dart_mapper_generator/lib/src/factories/default_expression_factory.dart	Local helper renamed from _buildDefaultExpr to buildDefaultExpr; its usage in submapperCall.ifNullThen(...) updated accordingly, with no logic changes.
Analyzer dependency bump packages/dart_mapper_generator/pubspec.yaml	analyzer dependency constraint updated from ^12.0.0 to ^13.0.0.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Poem

A hop, a skip, a name made new,
`buildDefaultExpr` shines right through.
Analyzer grows a version tall,
Two tiny changes, that is all!
🐇✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	No description was provided, so there is nothing substantive to assess.	Add a brief description of the dependency bump and refactor so reviewers can quickly understand the change.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the two main changes: analyzer bump and default-expression refactor.
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.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch bump-analyzer-version

---

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.}