Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should filter et al. pass on this.value as this.error? #6

Open
kwisatz opened this issue Nov 11, 2019 · 2 comments
Open

Should filter et al. pass on this.value as this.error? #6

kwisatz opened this issue Nov 11, 2019 · 2 comments

Comments

@kwisatz
Copy link
Member

kwisatz commented Nov 11, 2019

IMHO, after a filter, e.g. in a recover, recoverWhen or errorMap, it'd be useful to have the original value being passed on as this.error (without having to tap and store it in a variable of higher scope.

@floriansimon1
Copy link
Collaborator

IDK, people usually have a clear expectation of what filter means. Nobody ever complained that Array's filter doesn't preserve the original values.

However, there might be room for an additional utility function.

@kwisatz
Copy link
Member Author

kwisatz commented Nov 11, 2019 via email

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

No branches or pull requests

2 participants