Steff

@patroza another alternative to consider: **Option 1:** ```typescript class Person extends Schema.Class()({ name: Schema.string, createdAt: Schema.Date, posts: Schema.array(Schema.string), }) { constructor(data: { name: Person["name"] }) { super({ ...data, createdAt: new...

> This happened as both `DataTaggedError` and `SchemaTaggedError` are extended from `Error`, and for Error objects, now Vitest will only checks the `message` prop. > > https://github.com/vitest-dev/vitest/blob/c692f76e58ae11fcc13631adcb4b80055843d447/packages/expect/src/jest-utils.ts#L98 > > Perhaps...

Thanks @hi-ogawa and @fenghan34 for your quick response and solution. Another solution would be to simply `import * as assert from "node:assert"` and use it directly in test files, whenever...

> > Another solution would be to simply `import * as assert from "node:assert"` and use it directly in test files > > Just a note, Vitest supports extended assert...

Makes sense @hi-ogawa thanks for your contribution. Let's see if this behavior is really desired, to enable it by default.

> @gcanti I think this is user error in retrospect. The regex `/^[...]*$/` is effectively zero or more, so in that case it looks to be working as intended. It...

Hi @hi-ogawa it seems that I do not need anymore to use the custom matcher that you've initially provided. However, now I got the following issue (see below the last...