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
In 2.30.0 the following code gives a lot of warnings and suggests to import string, number, etc. instead of using the properties from the default import z.
In this case, I think it is clearer to continue prefixing the code with z and not using imported generic words like "string", "number" etc.
I'm not sure why the rule needed to be changed like this. The zod library is likely not the only case where such prefixing makes sense.
Would you be open to give an option to disable this behavior and only create warnings/errors for actual import statements?
I disabled the rule for now.
The text was updated successfully, but these errors were encountered:
In 2.30.0 the following code gives a lot of warnings and suggests to import
string
,number
, etc. instead of using the properties from the default import z.In this case, I think it is clearer to continue prefixing the code with z and not using imported generic words like "string", "number" etc.
I'm not sure why the rule needed to be changed like this. The zod library is likely not the only case where such prefixing makes sense.
Would you be open to give an option to disable this behavior and only create warnings/errors for actual import statements?
I disabled the rule for now.
The text was updated successfully, but these errors were encountered: