Skip to content

fix: do not default to none - #68

Merged
k223kim merged 1 commit into
mainfrom
remove-none-default
Sep 29, 2025
Merged

k223kim merged 1 commit into
mainfrom
remove-none-default

Conversation

@Danidapena

Copy link
Copy Markdown
Collaborator
Before submitting
  • Was this discussed/agreed via a Github issue? (no need for typos and docs improvements)
  • Did you read the contributor guideline, Pull Request section?
  • Did you make sure to update the docs?
  • Did you write any new necessary tests?

What does this PR do?

No all providers support "none". To avoid errors, do not default to "none"

PR review

Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in GitHub issues there's a high chance it will not be merged.

Did you have fun?

Make sure you had fun coding 🙃

@codecov

codecov Bot commented Sep 29, 2025 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84%. Comparing base (bef00d1) to head (3f9a175).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@        Coverage Diff         @@
##           main   #68   +/-   ##
==================================
- Coverage    84%   84%   -0%     
==================================
  Files         8     8           
  Lines       469   466    -3     
==================================
- Hits        393   390    -3     
  Misses       76    76           
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@k223kim
k223kim merged commit 1854f73 into main Sep 29, 2025
31 checks passed
@k223kim
k223kim deleted the remove-none-default branch September 29, 2025 18:37
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.

2 participants