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

tests(shorthand): allow non-strict assert #1845

Merged
merged 4 commits into from
Jul 21, 2017
Merged

Conversation

layershifter
Copy link
Member

@layershifter layershifter commented Jul 9, 2017

Why?

Extracted from #1795.

contains is too strict, we should allow non-strict assert in these cases, useless conditions should gone.

@codecov-io
Copy link

codecov-io commented Jul 9, 2017

Codecov Report

❗ No coverage uploaded for pull request base (master@b44760d). Click here to learn what that means.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff            @@
##             master    #1845   +/-   ##
=========================================
  Coverage          ?   99.75%           
=========================================
  Files             ?      145           
  Lines             ?     2477           
  Branches          ?        0           
=========================================
  Hits              ?     2471           
  Misses            ?        6           
  Partials          ?        0
Impacted Files Coverage Δ
src/elements/Input/Input.js 100% <100%> (ø)

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 b44760d...c639e34. Read the comment docs.

@@ -63,6 +63,7 @@ describe('Input', () => {
common.implementsHTMLInputProp(Input, {
alwaysPresent: true,
shorthandDefaultProps: { type: 'text' },
strictAssert: false,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about assertExactMatch or similar? It is not clear what is being strictly asserted.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, I like your suggestion, will change 👍

…b.com/Semantic-Org/Semantic-UI-React into tests/shorthand-strict

# Conflicts:
#	test/specs/commonTests/implementsShorthandProp.js
@layershifter
Copy link
Member Author

@levithomason I've changed an option name 👍

@levithomason levithomason merged commit 465b936 into master Jul 21, 2017
@levithomason levithomason deleted the tests/shorthand-strict branch July 21, 2017 15:29
@levithomason
Copy link
Member

Released in semantic-ui-react@0.71.2

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.

None yet

3 participants