unknownutil
unknownutil copied to clipboard
jsr-core
🦕 A lightweight utility pack for handling unknown type
- [x] :boom: Remove deprecated features - [x] :boom: Remove `isXXXXX` functions (only expose `is.XXXXX` functions) - etc.
Taking into account the potential for future advancements in Deno runtime, including tree shaking support, and various other factors, we initially exposed functions of the `isXXXXX` type. However, with the...
TypeScript offers the `Readonly` type function and the `readonly` keyword. However, the `isReadonlyOf` function seems a bit ambiguous. I propose the following improvements: - Enhance `isReadonlyOf` for Array, Tuple, and...
We have introduced a new metadata feature, providing us with the opportunity to implement improved error messages.
Like - `@core/unknownutil/is-any` - `@core/unknownutil/is-unknown` - ... So that user can import minimum requirements. This change may cause the recommended style change (e.g. prefer `isXXXXX` over `is.XXXXX`)
If `@core/errorutil` offers error alteration functions as proposed in https://github.com/jsr-core/errorutil/issues/3, I believe we can deprecate the `name` and `message` options in `assert` and `ensure`. I'd like to deprecate these options...
Assumed to use `SideEffect` for recording which part of the array/object attribute cause failer. Like ```ts export type SideEffect = (value: unknown) => void; export type Predicate = (x: unknown,...