import/no-named-as-default-member rule became less useful in 2.30.0

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.

Start by reproducing the warnings described for import/no-named-as-default-member with the Zod example and inspect the rule's existing tests or entry point. Define coverage for an option that suppresses warnings on default-import member usage while retaining warnings for actual import statements; done means the requested behavior is covered by regression tests.

Written by the indexing model from the issue text.