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

fix: Ambiguous default warning for no signature default #3378

Merged
merged 1 commit into from
Apr 12, 2024

Conversation

peterschutt
Copy link
Contributor

We now only issue a single warning for the case where a default value is supplied via Parameter() and not via a regular signature default.

Closes #3372

Description

Closes

We now only issue a single warning for the case where a default value is supplied via `Parameter()` and not via a regular signature default.

Closes #3372
Copy link

sonarcloud bot commented Apr 12, 2024

Copy link

codecov bot commented Apr 12, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.28%. Comparing base (40a5685) to head (f399608).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3378   +/-   ##
=======================================
  Coverage   98.28%   98.28%           
=======================================
  Files         323      323           
  Lines       14777    14778    +1     
  Branches     2347     2347           
=======================================
+ Hits        14523    14524    +1     
  Misses        116      116           
  Partials      138      138           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link

Documentation preview will be available shortly at https://litestar-org.github.io/litestar-docs-preview/3378

@peterschutt peterschutt merged commit 7b93d97 into main Apr 12, 2024
28 checks passed
@peterschutt peterschutt deleted the 3372-ambig-default-warning branch April 12, 2024 06:20
peterschutt added a commit that referenced this pull request May 1, 2024
We now only issue a single warning for the case where a default value is supplied via `Parameter()` and not via a regular signature default.

Closes #3372

(cherry picked from commit 7b93d97)
peterschutt added a commit that referenced this pull request May 2, 2024
We now only issue a single warning for the case where a default value is supplied via `Parameter()` and not via a regular signature default.

Closes #3372

(cherry picked from commit 7b93d97)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bug: Improve warning message for ambiguous defaults
2 participants