Are you open to support `context` as `describe` alias?

Up until around 1 year ago, context was an officially supported describe alias, but later got removed. Still, because of its value, some people (myself included) still want to use it, and as explained on that issue it’s very easy to add it back.

Unfortunately, it’s not compatible with using this ESLint plugin (and I really like this plugin 😃 ). Would you be open to merge a PR adding context (and derived context.only, …) to the describe aliases and other places where it would be needed?

I understand maybe you wouldn’t want to have defaults that are different to what jest itself has in terms of globals, but if so, maybe adding it as a configurable option instead? Afaik, the plugin itself cannot receive a configuration though, so apparently that would need to be done by passing options to each applicable rule.

If you are open to this I can give a PR a try. Or if you have any other suggestion on how to use ´context´ and this plugin at the same time, I would love to hear it.

Thanks for this plugin!

[raulmt]

@leoneves no, I haven’t done this yet, sorry…

[github-actions[bot]]

🎉 This issue has been resolved in version 26.5.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀