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

find() operator #7

Closed
felixfbecker opened this issue Apr 14, 2017 · 2 comments · Fixed by #19
Closed

find() operator #7

felixfbecker opened this issue Apr 14, 2017 · 2 comments · Fixed by #19

Comments

@felixfbecker
Copy link
Owner

No description provided.

@lazarljubenovic
Copy link
Contributor

What do you think about adding a findOrThrow as well? I find myself very often doing the pattern of throwing if the result is undefined. A lot of times, I know it has to be there and if it's not there, something is wrong in my logic. A lib for AST manipulation I'm using has a lot of pairs like that and I'm loving it.

lazarljubenovic added a commit to lazarljubenovic/iterare that referenced this issue Jun 24, 2018
lazarljubenovic added a commit to lazarljubenovic/iterare that referenced this issue Jun 24, 2018
lazarljubenovic added a commit to lazarljubenovic/iterare that referenced this issue Jun 25, 2018
felixfbecker pushed a commit that referenced this issue Oct 2, 2018
@felixfbecker
Copy link
Owner Author

🎉 This issue has been resolved in version 1.1.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants