Maybe.maybe has wrong type (or wrong document)
See original GitHub issueMaybe.maybe
has <T>(t: T): Maybe<T>
type,
but its document says
A Maybe object containing the value passed in input. If t is null or undefined, the Maybe object is filled with Nothing.
Therefore, at least I think, right type is <T>(t?: T): Maybe<T>
or <T>(t: T | undefined | null): Maybe<T>
.
Is there any problem for these types?
Issue Analytics
- State:
- Created 7 years ago
- Reactions:3
- Comments:7 (6 by maintainers)
Top Results From Across the Web
[Typscript] Wrong type for `new Model(doc)` · Issue #10302
When using new Model(doc) to create a new model and the save() it. the type of doc is always any which break the...
Read more >Typescript: Type 'string | undefined' is not assignable to ...
For example my .env file has a value that I can trust will always be there, but using my env variable inside a...
Read more >An incorrect structure was found in the pdf file
Solved: I am trying to move one page in the thumbnails view of a 16 page pdf. When I drag and drop the...
Read more >LaTeX Error: Something's wrong--perhaps a missing \item - ...
Your bbl file has no \bibitem . Regenerate it running BibTeX; you need at least one \cite (or \nocite ) command in your...
Read more >invalid argument [1]: wrong type [not a pair];Error Object: #f
The error message indicates that there is an error in the scheme code. A list value is needed, but a boolean value "#f"...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
That would be most welcome 😃
Closing this thanks to @piq9117’s contribution 😃