Incorrect detection of properties of t.context as AVA functions

[GMartigny]

Hi,
When a property of t.context match an existing AVA function (say end), the eslint plugin fire an error for incorrect use of this function.
Consider:

test.beforeEach((t) => {
    t.context = new Vector(1, 2);
});
test("constructor", (t) => {
    t.is(t.context.start, 1);
    t.is(t.context.end, 2);		// <= `t.end()` should only be used inside of `test.cb()`  ava/no-invalid-end
});

I have search the source and it appear that only end and skip raised the issue.

gmartigny earned $40.00 by resolving this issue!

• Checkout the Issuehunt explorer to discover more funded issues.
• Need some help from other developers? Add your repositories on Issuehunt to raise funds.

[novemberborn]

I suppose nameOfRootObject doesn't do what we think it does:

eslint-plugin-ava/rules/no-invalid-end.js

Line 17 in c5a77bb

util.nameOfRootObject(node) === 't'

It's used in some other rules too: https://github.com/avajs/eslint-plugin-ava/search?q=nameofrootobject&unscoped_q=nameofrootobject

[IssueHuntBot]

@IssueHunt has funded $40.00 to this issue.

---

• Submit pull request via IssueHunt to receive this reward.
• Want to contribute? Chip in to this issue via IssueHunt.
• Checkout the IssueHunt Issue Explorer to see more funded issues.
• Need help from developers? Add your repository on IssueHunt to raise funds.

[IssueHuntBot]

@sindresorhus has rewarded $36.00 to @GMartigny. See it on IssueHunt

• 💰 Total deposit: $40.00
• 🎉 Repository reward(0%): $0.00
• 🔧 Service fee(10%): $4.00