-
Notifications
You must be signed in to change notification settings - Fork 31
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
Bring test coverage to 100% #87
Labels
Comments
This was referenced Sep 17, 2024
francisfuzz
pushed a commit
that referenced
this issue
Sep 18, 2024
…100) <!-- This pull request template provides suggested sections for framing your work. You're welcome to change or remove headers if it doesn't fit your use case. :) --> ### What are you trying to accomplish? Improve test coverage for `parse.js` file. Concretely for `getUserConfirmation()` method. relates to #87
yoooo @oscard0m so nice to see you contribute ❤ |
This was referenced Sep 18, 2024
gr2m
pushed a commit
that referenced
this issue
Sep 18, 2024
### What are you trying to accomplish? - **test(prompt): add 100% test coverage for `parsePromptArguments()`** - **test(prompt): add test coverage for prompt.stream()** ### Context Relates to #87 <!-- This pull request template provides suggested sections for framing your work. You're welcome to change or remove headers if it doesn't fit your use case. :) ### What are you trying to accomplish? ### What approach did you choose and why? ### What should reviewers focus on? -->
🎉 This issue has been resolved in version 5.0.1 🎉 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
Now that we have test coverage enabled via #86 thanks to @artifactz1, we can address the parts of the code that are not yet covered and do so. Where applicable, lines or branches can also be ignored, see syntax
The text was updated successfully, but these errors were encountered: