Skip to content

fix(warnings): do not trigger MiscalledStubWarnings from prop events #126

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

Merged
merged 1 commit into from
Mar 25, 2022

Conversation

mcous
Copy link
Owner

@mcous mcous commented Mar 24, 2022

Closes #125

@codecov
Copy link

codecov bot commented Mar 24, 2022

Codecov Report

Merging #126 (d887d5f) into main (5db349b) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #126   +/-   ##
=======================================
  Coverage   98.29%   98.29%           
=======================================
  Files          19       19           
  Lines         703      704    +1     
  Branches      119      120    +1     
=======================================
+ Hits          691      692    +1     
  Misses         10       10           
  Partials        2        2           
Impacted Files Coverage Δ
decoy/warning_checker.py 100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5db349b...d887d5f. Read the comment docs.

@mcous mcous merged commit 396eae2 into main Mar 25, 2022
@mcous mcous deleted the fix-prop-warnings branch March 25, 2022 02:35
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.

Property get stubs cause spurious MiscalledStubWarnings
1 participant