Skip to content

🧹 Remove dead code in _enumFieldsMap#194

Open
kevmoo wants to merge 1 commit intomasterfrom
fix-dead-code-enum-helpers-4810040716243885101
Open

🧹 Remove dead code in _enumFieldsMap#194
kevmoo wants to merge 1 commit intomasterfrom
fix-dead-code-enum-helpers-4810040716243885101

Conversation

@kevmoo
Copy link
Owner

@kevmoo kevmoo commented Mar 24, 2026

This PR addresses a dead code issue in build_cli/lib/src/enum_helpers.dart flagged by the Dart analyzer. The _enumFieldsMap function contained a trailing return null that was unreachable due to its preceding logic and the context in which it was used. I refactored the function and its public wrapper enumValueMapFromType to use non-nullable return types and explicit casting to EnumElement, as these functions are only called after the type has been verified as an enum. I also updated the primary call site in build_cli_generator.dart to reflect these changes. I've verified that the analyzer warning is resolved.


PR created automatically by Jules for task 4810040716243885101 started by @kevmoo

Refactor `_enumFieldsMap` and `enumValueMapFromType` in `build_cli/lib/src/enum_helpers.dart` to eliminate an unreachable `return null` and redundant null checks.

- Changed `_enumFieldsMap` to return `Map<FieldElement, String>` (non-nullable) and use an explicit cast to `EnumElement` for the target type's element, as it's only called for enums.
- Updated `enumValueMapFromType` to return `String` (non-nullable) and removed the now unnecessary null check.
- Cleaned up the call site in `build_cli/lib/src/build_cli_generator.dart` to remove a redundant bang operator.

Co-authored-by: kevmoo <17034+kevmoo@users.noreply.github.com>
@google-labs-jules
Copy link
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@gemini-code-assist
Copy link

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request improves code quality and type safety within the build_cli package by eliminating dead code and strengthening type guarantees. It converts nullable return types to non-nullable ones in enum-related helper functions and updates a corresponding call site, thereby resolving a Dart analyzer warning.

Highlights

  • Dead Code Removal: Removed an unreachable return null statement from the _enumFieldsMap function, addressing a Dart analyzer warning.
  • Type Safety Enhancement: Refactored _enumFieldsMap and enumValueMapFromType to use non-nullable return types, ensuring these functions always return a valid map or string, respectively, given their usage context.
  • Explicit Type Casting: Introduced an explicit cast of targetType.element to EnumElement within _enumFieldsMap, reinforcing the assumption that the type is always an enum when this function is called.
  • Call Site Update: Modified the primary call site in build_cli_generator.dart to remove the null-assertion operator (!), aligning with the new non-nullable return type of enumValueMapFromType.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request effectively removes dead code from _enumFieldsMap and improves type safety by making return types non-nullable. The changes in enumValueMapFromType and its call site in build_cli_generator.dart are consistent with this refactoring. I've added one suggestion to improve the readability of how enum constants are retrieved.

Comment on lines +26 to +28
element.fields
.where((p) => p.isOriginDeclaration)
.map((p) => MapEntry(p, p.name!)),

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

For better readability and to more directly express the intent, you can use element.constants to get the enum constants instead of filtering element.fields.

Suggested change
element.fields
.where((p) => p.isOriginDeclaration)
.map((p) => MapEntry(p, p.name!)),
element.constants.map((p) => MapEntry(p, p.name!))

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant