-
When passing properties to a component, would you prefer that the properties are type checked and throw an exception in case of wrong type, or rather allow JavaScript to implicitly type coerce, i.e., …
-
Hello everyone, first : thanks for this incredible library, look like the best in functionnal programmin in Ts
In the basic example
```
const res = pipe(
[1, 2, 3, 4, 5], // → [1, 2, 3, 4, …
-
#### Description
Currently, in estimator methods like `_check_dictionary_compatibility`, numerical types are coerced to categorical types.
However, other type incompatibilities are not coerced and e…
-
### Description
The following code:
```php
-
### Minimal reproducible example
https://github.com/jowparks/ios-expo-data-bug
### What platform(s) does this occur on?
iOS
### Did you reproduce this issue in a development build?
Yes
### Summa…
-
It'd be nice to be able to coerce convertible types to other types.
``` js
const PersonRecord = Record({
id: String,
phone: Coerce(Union(Number, String), String),
}, 'Person');
```
In this hypot…
-
### Description
Hi
This library is great, well documented and well thought-out, thanks for the work you've put into it!
I'm the lead maintainer of https://github.com/langchain-ai/langgraph and …
-
It would be nice to have a custom coertion/parsing function beyond the generic type based ones. Something like:
(define/provide-environment [id #:coerse my-parse])
This would allow types beyond the …
-
Would you add this overload?
```
'&{}' => sub { my $x = shift; sub { ${ $x } } },
```
It will allow the following to work
```
package Test;
use boolean;
use Types::Standard qw( Bool );
use Moo;
has…
-
Thank you for getting involved with Okta's Developer Docs!
**Affected page(s):**
- [https://developer.okta.com/docs/reference/core-okta-api/](https://developer.okta.com/docs/reference/core-okta-ap…