How to disable lint/style/useNamingConvention for object properties that are out of my control?

[mkvlrn]

Checking the options for the rule I couldn't figure out how to not have warns raised in properties that are defined in imported libs, for example, zod's RawCreateParams when defining zod schemas:

A big enough schema could have a dozen of those, and disabling each by comment is not viable.

The argument for that is defined in zod like this:

export type RawCreateParams = {
    errorMap?: ZodErrorMap;
    invalid_type_error?: string;
    required_error?: string;
    message?: string;
    description?: string;
} | undefined;

For now I'm overriding my schema files to disable the rule, but I would like to keep the rule on and have it not affect types coming from zod or any other imported lib.

Is there a way to do this that I really missed in the docs?

[ematipico]

cc @Conaclos

[Conaclos]

It is currently not possible to configure what you want.
I could advise relaxing the convention for object literal properties:

	"linter": {
		"enabled": true,
		"rules": {
			"recommended": true,
			"style": {
				"useNamingConvention": {
					"level": "error",
					"options": {
						"conventions": [
							{
								"selector": {
									"kind": "objectLiteralProperty"
								},
								"formats": ["camelCase", "snake_case"]
							}
						]
					}
				}
			}
		}
	},

Another possibility is to add exceptions for some property names:

	"linter": {
		"enabled": true,
		"rules": {
			"recommended": true,
			"style": {
				"useNamingConvention": {
					"level": "error",
					"options": {
						"conventions": [
							{
								"selector": {
									"kind": "objectLiteralProperty"
								},
								"match": "invalid_type_error|required_type_error|(.*)"
							}
						]
					}
				}
			}
		}
	},

[mkvlrn]

Alright, I think using a combination of override for the schema files and narrowing down with exceptions to property names is solid enough!

Is there a possibility of adding options to prevent warnings in such cases in the future?

[Conaclos]

Is there a possibility of adding options to prevent warnings in such cases in the future?

What do you mean? I don't understand.

[mkvlrn]

Those property names come from the zod library:

https://github.com/colinhacks/zod/blob/f7ad26147ba291cb3fb257545972a8e00e767470/src/types.ts#L117-L125

So the naming convention is being broken by imported code that we can't/shouldn't modify. Adding the exceptions like I'm doing is not a big deal at all, but one could infer from the warning that my code violated the naming convention, and it could be a bit misleading to someone reviewing it.

Adding the explanation for the exception is enough, but I was wondering if it is something that could be "understood" by biome.

I'm sorry if I'm not making myself clear; English is not my primary language and sometimes meaning gets lost! 🇧🇷

[Conaclos]

I see. Unfortunately this could require to make the rule aware of types. Biome is currently not able to get type info. Moreover, I am unsure if it makes sense of making the rule so capable. I am still pen for simpler suggestions that could improve the capabilities of the rule.

[mkvlrn]

Oh, that makes sense. Overriding and adding specific exceptions works great for me. Thanks for taking the time!