Skip to content

Add ambiguity test #169

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
Jan 8, 2022
Merged

Add ambiguity test #169

merged 1 commit into from
Jan 8, 2022

Conversation

sungam3r
Copy link
Member

@sungam3r sungam3r commented Jan 8, 2022

fixes #127

@sungam3r sungam3r self-assigned this Jan 8, 2022
@github-actions github-actions bot added the test Pull request that adds new or changes existing tests label Jan 8, 2022
@sungam3r sungam3r added this to the 8.0 milestone Jan 8, 2022
@codecov-commenter
Copy link

Codecov Report

Merging #169 (88d864e) into master (5aed200) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #169   +/-   ##
=======================================
  Coverage   86.98%   86.98%           
=======================================
  Files          83       83           
  Lines        4088     4088           
  Branches      388      388           
=======================================
  Hits         3556     3556           
  Misses        488      488           
  Partials       44       44           

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 5aed200...88d864e. Read the comment docs.

@sungam3r sungam3r merged commit 164686e into master Jan 8, 2022
@sungam3r sungam3r deleted the strict branch January 8, 2022 10:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
test Pull request that adds new or changes existing tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Avoid parse ambiguity on types & extensions
2 participants