refactor: migrate member_ordering rule#297
Conversation
|
/gemini review |
There was a problem hiding this comment.
Code Review
This pull request refactors the member_ordering lint rule to extend SolidMultiLintRule (a new base class for rules with multiple diagnostic codes), splits several model classes into separate files, and replaces the old test file with a comprehensive unit test suite. The review feedback correctly identifies two critical compilation errors in MemberOrderingVisitor: first, the use of the non-existent BlockClassBody class, and second, attempting to access a .name property on ConstructorDeclaration.typeName (which is a Token and should use .lexeme instead).
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
| } | ||
| } | ||
|
|
||
| if (!_parameters.alphabetize && _parameters.alphabetizeByType) { |
There was a problem hiding this comment.
| if (!_parameters.alphabetize && _parameters.alphabetizeByType) { | |
| else if (_parameters.alphabetizeByType) { |
|
|
||
| @override | ||
| List<MemberInfo> visitClassDeclaration(ClassDeclaration node) { | ||
| void visitClassDeclaration(ClassDeclaration node) { |
There was a problem hiding this comment.
I think some of the blocks in this method should be extracted:
void _visitClassDeclaration(ClassDeclaration node) {
final type = node.extendsClause?.superclass.type;
final isFlutterWidget =
isWidgetOrSubclass(type) || isWidgetStateOrSubclass(type);
final body = node.body;
if (body is BlockClassBody) {
for (final member in body.members) {
if (member is FieldDeclaration) {
_visitFieldDeclaration(member, isFlutterWidget);
} else if (member is ConstructorDeclaration) {
_visitConstructorDeclaration(member, isFlutterWidget);
} else if (member is MethodDeclaration) {
_visitMethodDeclaration(member, isFlutterWidget);
}
}
}
}
void _reportWrongOrder() {
final wrongOrderMembers = _membersInfo.where(
(info) => info.memberOrder.isWrong,
);
for (final memberInfo in wrongOrderMembers) {
final memberGroup = memberInfo.memberOrder.memberGroup;
final previousMemberGroup = memberInfo.memberOrder.previousMemberGroup;
_rule.reportAtNode(
memberInfo.classMember,
diagnosticCode: MemberOrderingRule.wrongOrderCode,
arguments: [
memberGroup.toString(),
previousMemberGroup?.toString() ?? '',
],
);
}
}
void _reportAlphabeticalOrder() {
final alphabeticallyWrongOrderMembers = _membersInfo.where(
(info) => info.memberOrder.isAlphabeticallyWrong,
);
for (final memberInfo in alphabeticallyWrongOrderMembers) {
final names = memberInfo.memberOrder.memberNames;
_rule.reportAtNode(
memberInfo.classMember,
diagnosticCode: MemberOrderingRule.alphabeticalOrderCode,
arguments: [
names.currentName,
names.previousName ?? '',
],
);
}
}
void _reportAlphabeticalTypeOrder() {
final alphabeticallyByTypeWrongOrderMembers = _membersInfo.where(
(info) => info.memberOrder.isByTypeWrong,
);
for (final memberInfo in alphabeticallyByTypeWrongOrderMembers) {
final names = memberInfo.memberOrder.memberNames;
_rule.reportAtNode(
memberInfo.classMember,
diagnosticCode: MemberOrderingRule.alphabeticalByTypeOrderCode,
arguments: [
names.currentName,
names.previousName ?? '',
],
);
}
}
void _reportMembers(bool Function(MemberInfo) filter, DiagnosticCode code) {
final filtered = _membersInfo.where(filter);
for (final memberInfo in filtered) {
final names = memberInfo.memberOrder.memberNames;
_rule.reportAtNode(
memberInfo.classMember,
diagnosticCode: code,
arguments: [
names.currentName,
names.previousName ?? '',
],
);
}
}
// Similar repetition in _visitX
I feel like we should also extract the bool _isXGroup methods into an extension on MemberGroup and move it to a separate file
Closes #252