traverse1984 oxide.ts issues

traverse1984 / oxide.ts

Rust's Option<T> and Result<T, E>, implemented for TypeScript.

MIT License

509 stars 19 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Unexpected TypeScript behavior with Option, Some and None

#23 Kolobamanacas opened 2 weeks ago
2
andThen "f" argument is wrongfully typed

#22 SteakOvercooked closed 8 months ago
0
Angular warning

#21 kiranpradeep opened 8 months ago
0
Pipe Operator

#20 ayazemregm opened 1 year ago
0
Chaining methods don't allow varying secondary type parameter

#19 Alexander-Prime opened 1 year ago
4
Change `type` exports into `interface` exports

#18 Asha20 opened 1 year ago
0
using match to return a Result gives an error

#17 joelgrus closed 1 year ago
1
Fix exports in package.json

#16 yaser-abclabs closed 1 year ago
1
Working on next release - any suggestions?

#15 traverse1984 opened 1 year ago
13
Should intoTuple use undefined instead of null?

#14 traverse1984 closed 1 year ago
5
Async API

#13 sidiousvic opened 1 year ago
11
Add intoTuple

#12 sidiousvic closed 1 year ago
4
Add intoTuple

#11 sidiousvic closed 1 year ago
3
I think there should be a API for unwrapping Results into tuples

#10 thelinuxlich closed 1 year ago
3
'.ts' is not a valid suffix for a module - Consider renaming the repo.

#9 rrichardson closed 2 years ago
4
Add `Result.fromCb` Method

#8 kadiryazici closed 2 years ago
3
refactored Option and Result to use a single class plus statics

#7 rrichardson closed 2 years ago
3
Adds flatten() to Option and Result

#6 rrichardson closed 2 years ago
5
flatten() for Result and Option and nested Ok()'s

#5 rrichardson closed 2 years ago
2
Expose ResultType under core?

#4 rrichardson closed 2 years ago
6
Webpack chokes on version 1.0.0

#3 najamelan closed 2 years ago
4
Unexpected Type Strictness with `unwrap_or`

#2 alexlafroscia closed 2 years ago
1
unwrap_or -> unwrapOr

#1 linonetwo closed 2 years ago
3