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(model): throw for invalid include type #10527

merged 1 commit into from Mar 9, 2019


Copy link

Pull Request check-list

Please make sure to review and check all of these items:

  • Does npm run test or npm run test-DIALECT pass with this change (including linting)?
  • Does the description below contain a link to an existing issue (Closes #[issue]) or a description of the issue you are solving?
  • Have you added new tests to prevent regressions?
  • Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?
  • Did you follow the commit message conventions explained in

Description of change

Fixes #10426

Copy link

codecov bot commented Mar 9, 2019

Codecov Report

Merging #10527 into master will increase coverage by <.01%.
The diff coverage is 96.15%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master   #10527      +/-   ##
+ Coverage   96.14%   96.14%   +<.01%     
  Files          92       92              
  Lines        9500     9504       +4     
+ Hits         9134     9138       +4     
  Misses        366      366
Impacted Files Coverage Δ
lib/model.js 96.66% <96.15%> (ø) ⬆️

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 0b5aa71...9502d60. Read the comment docs.

@sushantdhiman sushantdhiman merged commit 454cf48 into master Mar 9, 2019
@sushantdhiman sushantdhiman deleted the error-for-include-conforming branch March 9, 2019 08:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

Successfully merging this pull request may close these issues.

None yet

1 participant