Reported errors don't agree with TypeScript IDE / CLI about vite-plugin-vitest-typescript-assert HOT 7 CLOSED

@jasonkuhrt I really need to add more documentation to this project. Ideally I would like to use tsc directly but unfortunately I haven't found a way to do it and I don't think it's possible (but you never know until someone does). However, it is possible to make a plugin for vscode that could report the errors in the IDE (not in the near future). In any case, thank you for reporting.

from vite-plugin-vitest-typescript-assert.

@jasonkuhrt This is the expected behaviour, expectType is doing a strict type equality comparison and in this case the input parameter in your create function is not a simple Record but an intersection of several Zod objects. In this case, if your goal is not to test the type equality but its assignability you should use expectAssignable.

from vite-plugin-vitest-typescript-assert.

@jasonkuhrt Maybe you want to test the tssert API which is a bit more flexible and less ambiguous. Both APIs can be used at the same time, which allows for testing and gradual transition.

from vite-plugin-vitest-typescript-assert.

@skarab42 Do you agree it is incorrect that the IDE and Vitest output disagree though? When I type check the codebase with tsc I also see no error (agrees with IDE).

from vite-plugin-vitest-typescript-assert.

@jasonkuhrt I don't see any errors in the IDE except the warning that says to avoid using unbound methods.

from vite-plugin-vitest-typescript-assert.

Sorry I misunderstood the question. It's normal not to have the error in the IDE nor with tsd. If you look at the implementation of the expectType function you see that it does strictly nothing and accepts all types/values (this is not really true). When the plugin encounters this function then it calls a custom version of the TS compiler to perform the type tests.

from vite-plugin-vitest-typescript-assert.

@skarab42 Ahhhh. Ok did not expect that. Do you prefer to work this way? Does it have to be this way? Is the idea to centralize all the "feedback" into one consistent place?

Not sure what I think yet. But I think I'd want to see the error show up outside of Vitess.

from vite-plugin-vitest-typescript-assert.