question : a function named pending () triggered the 'no-disabled-tests' error. my bad?

[lsuarez-tiempo-dev]

I just read that pending is a jasmine global that allows you not run the test.
effectively disabling it.

Our code imports a value and then runs its it.
It appears the parser is confusing it with the jasmine global.
without being to careful with the syntax, This is basically what we're doing:

import { pending } from './myActions' ; 

describe('the pending action creator should return correct object', ()=>{
    it('should work correctly' , ()=>{
      expect(pending()).toStrictEqual({type:'FETCH_ALL_ALBUMS_PENDING'});
   })
})

does this rule notice if you import the function before assuming you're using the jasmine global and hence, disabling the test?
or is it an issue with the code?

[SimenB]

A PR fixing this would be most welcome! We should only detect usage of a global pending calls, not locally declared or imported ones

[macklinu]

I'll push up a PR for this one. 👍

[SimenB]

🎉 This issue has been resolved in version 21.22.1 🎉

The release is available on:

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

Your semantic-release bot 📦🚀