Skip to content
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
feat: Loosen @typescript-eslint/naming-convention for object litera…
…l properties

The rule `@typescript-eslint/naming-convention` has been updated to no
longer enforce a naming convention for object literal properties. This
too often needs to be disabled because of the naming conventions of 3rd
party libraries/services that we don't control, which can require
object-literal parameters.

Closes #323
  • Loading branch information
Gudahtt committed Dec 2, 2025
commit 06a8c14b0f928f11e50d92d683b639e3393a0084
5 changes: 1 addition & 4 deletions packages/typescript/rules-snapshot.json
Original file line number Diff line number Diff line change
Expand Up @@ -29,10 +29,7 @@
"selector": "objectLiteralMethod",
"format": ["camelCase", "PascalCase", "UPPER_CASE"]
},
{
"selector": "objectLiteralProperty",
"format": ["camelCase", "PascalCase", "UPPER_CASE"]
},
{ "selector": "objectLiteralProperty", "format": null },
{ "selector": "typeLike", "format": ["PascalCase"] },
{
"selector": "typeParameter",
Expand Down
4 changes: 3 additions & 1 deletion packages/typescript/src/index.mjs
Original file line number Diff line number Diff line change
Expand Up @@ -113,7 +113,9 @@ const config = createConfig({
},
{
selector: 'objectLiteralProperty',
format: ['camelCase', 'PascalCase', 'UPPER_CASE'],
// Disabled because object literals are often parameters to 3rd party libraries/services,
// which we don't set the naming conventions for
format: null,
},
{
selector: 'typeLike',
Expand Down
Loading