feat: Loosen @typescript-eslint/naming-convention for object literal properties
#428
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.
The rule
@typescript-eslint/naming-conventionhas 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
Note
Stops enforcing naming conventions for
objectLiteralPropertyin the TypeScript ESLint config; updates snapshot and changelog accordingly.packages/typescript/src/index.mjs):@typescript-eslint/naming-conventionby settingobjectLiteralPropertyformat: null(with comment explaining third-party params).packages/typescript/rules-snapshot.json):objectLiteralPropertychange toformat: null.packages/typescript/CHANGELOG.md):Written by Cursor Bugbot for commit 2e72fb7. This will update automatically on new commits. Configure here.