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

no unused expression #814

Closed
fibo opened this issue Mar 5, 2017 · 2 comments

Comments

@fibo
Copy link

commented Mar 5, 2017

I have a test like this

describe('emptyGraph', function () {
  it('is a valid graph', function () {
    validate(emptyGraph).should.be.ok
  })
})

and now standard v9 complains with

Expected an assignment or function call and instead saw an expression

Why it is considered a warning? I don't get it. How it could be rewritten?

@fibo fibo changed the title no unsed expression no unused expression Mar 5, 2017

@dcousens

This comment has been minimized.

Copy link
Member

commented Mar 5, 2017

Duplicate of #803, see #690

Specifically, here is the comment that explains what you can do to fix the issue: #690 (comment)

@dcousens dcousens closed this Mar 5, 2017

@dcousens dcousens added the question label Mar 5, 2017

@fibo

This comment has been minimized.

Copy link
Author

commented Mar 6, 2017

Thank you for the asnwer, it was solved using

 validate(emptyGraph).should.be.True()

@lock lock bot locked as resolved and limited conversation to collaborators May 10, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
2 participants
You can’t perform that action at this time.