Daniel Breiner
Daniel Breiner
In some cases, it might be desirable to abort early in any of the type specific validations - checks - like `.min`, `.url`, `.regex` and so on. An example of...
Closes #1603 `CustomErrorParams` is not used anywhere else besides `refine`, so it should be fine to add the `fatal` field directly there. The object gets then passed to `ctx.addIssue`.
As mentioned in https://github.com/colinhacks/zod#abort-early, chained refinements are all executed, which may not be desirable in all cases. That is why `superRefine` has a way of _aborting early_ - preventing further...
Validation continues after an unsuccessful refine(), which gives it an incorrect return type and can make subsequent effects unexpectedly throw. Code: ```ts import { z } from 'zod'; const isNotNull...
Currently, `refine` has a type guard which is used to narrow down the output type. ```js refine( check: (arg: Output) => arg is RefinedOutput, message?: /* ... */ ): ZodEffects;...
Currently, the filename from which the project is being loaded is used as the project name. I propose using the `name` field in `makeProject`. Also, consider showing a warning when...
Title. Under the project selection button or maybe on the bottom of that panel?
Closes #345
The general problem is always opacity < 1 making elements fuzzy and blurry. Then a hard jump to the correct pretty crispness when it gets set to 1. Now in...
Title. Tested in Firefox and Chrome, seems to be behaving the same. ```ts import { Rect, Text } from "@motion-canvas/2d/lib/components"; import { makeScene2D } from "@motion-canvas/2d/lib/scenes"; import { waitFor }...