Skip to content

Conversation

@GregOnNet
Copy link
Contributor

@GregOnNet GregOnNet commented Mar 17, 2025

To-do

  • Handle one successful ResultAsync
  • Handle failed ResultAsync
  • Handle collection of ResultAsync
  • Handle one resolved Promise
  • Handle rejected Promise
  • Handle collection of ResultAsync | Promise
  • Handle successful Result
  • Handle failed Result
  • Handle collection of ResultAsync | Result
  • Add combineAsync to Result<T>
  • Clean up code

Closes #27

@GregOnNet GregOnNet force-pushed the feature/combine-async branch from c65812f to a0fd2c1 Compare March 17, 2025 12:55
@GregOnNet GregOnNet changed the title chore(vscode): accept automatic change made by vsCode feat: conbineAsync Mar 17, 2025
@GregOnNet GregOnNet force-pushed the feature/combine-async branch from 36eb330 to 54b4e7b Compare March 18, 2025 09:12
- it technically works fine
- but Promise Error is not the same as a Failure
- so we need to guess the error message and we do not know the type of the error of the promise
- it is better to wrap the Promise in a ResultAsync first specifying a human readable failure
@GregOnNet GregOnNet marked this pull request as ready for review March 18, 2025 12:58
@GregOnNet GregOnNet requested a review from seangwright March 24, 2025 05:45
@GregOnNet
Copy link
Contributor Author

@seangwright thid PR is ready to Review.

@seangwright seangwright merged commit 62ccfb0 into seangwright:main Apr 8, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Feature: combineAsync

2 participants