You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/linters.md
+7-8Lines changed: 7 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -638,16 +638,15 @@ lintersConfig:
638
638
The `noreferences` linter can automatically fix field names in **PreferAbbreviatedReference mode**:
639
639
640
640
**PreferAbbreviatedReference mode:**
641
-
- Replaces 'Reference' with 'Ref' and 'References' with 'Refs' at the start or end of field names
642
-
-This avoids false positives for words like "Preference" where "eference" appears in the middle
641
+
- Replaces 'Reference' with 'Ref' and 'References' with 'Refs' anywhere in field names
642
+
-Case insensitive matching
643
643
- Examples:
644
-
-`NodeReference` → `NodeRef` (end)
645
-
-`ReferenceNode` → `RefNode` (start)
646
-
-`NodeReferences` → `NodeRefs` (end)
647
-
-`ReferencesCount` → `RefsCount` (start)
648
-
-`PreferenceType` → no change (middle - not flagged)
644
+
-`NodeReference` → `NodeRef`
645
+
-`ReferenceNode` → `RefNode`
646
+
-`NodeReferences` → `NodeRefs`
649
647
650
-
**Note:** NoReferences policy does not provide automatic fixes. It only reports warnings to inform developers about the presence of reference-related words in field names.
648
+
**Note:**
649
+
- The `NoReferences` mode only reports warnings without providing fixes, allowing developers to choose appropriate field names manually.
0 commit comments