feat: add unnecessary_type_name_in_constructor rule - #232
Merged
Conversation
Closes #220 Co-authored-by: marcossevilla <marcossevilla@users.noreply.github.com>
marcossevilla
previously approved these changes
Aug 17, 2026
marcossevilla
approved these changes
Aug 17, 2026
github-project-automation
Bot
moved this from Needs Triage
to Done
in VGV Open Source 馃 馃馃専
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Enables the
unnecessary_type_name_in_constructorlint rule introduced in Dart 3.13, which warns when a type name is unnecessarily used in a constructor invocation.Changes
unnecessary_type_name_in_constructortoanalysis_options.11.0.0.yamlexclusion_reasons.jsonandREADME.mdCloses #220