Skip to content

fix: try other resovlers when answers are empty#34

Merged
achingbrain merged 1 commit into
mainfrom
fix/try-other-resolvers-when-answers-are-empty
Jun 25, 2026
Merged

fix: try other resovlers when answers are empty#34
achingbrain merged 1 commit into
mainfrom
fix/try-other-resolvers-when-answers-are-empty

Conversation

@achingbrain

Copy link
Copy Markdown
Member

If a resolver returns an empty answer array, try other resolvers until we either run out of resolvers or an answer is found.

If a resolver returns an empty answer array, try other resolvers
until we either run out of resolvers or an answer is found.
@achingbrain achingbrain merged commit 747c5fe into main Jun 25, 2026
40 of 43 checks passed
@achingbrain achingbrain deleted the fix/try-other-resolvers-when-answers-are-empty branch June 25, 2026 08:36
github-actions Bot pushed a commit that referenced this pull request Jun 25, 2026
## [1.0.15](v1.0.14...v1.0.15) (2026-06-25)

### Bug Fixes

* try other resovlers when answers are empty ([#34](#34)) ([747c5fe](747c5fe))

### Trivial Changes

* bump sinon from 21.1.2 to 22.0.0 ([#27](#27)) ([8f7132b](8f7132b))
@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version 1.0.15 🎉

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant