5
77%
master: 77%

Ran 09 Feb 2020 10:02PM UTC

Files 10

Run time 0s

Badge

Embed ▾

Committed 09 Feb 2020 10:02PM UTC coverage: 75.182%. First build

Job # EXECUTE_CS_CHECK=true EXECUTE_COVERAGE=true

Build Type

Pull #34

travis-ci

Committed by Rami Massoud

Commit Message

Need to use isset instead of property_exists

Seems there is a weird tension in the use of ArrayObject where you
can't use array_key_exists because it is still an object, but it can
have keys/values like one. Looking at a sample response, `next_cursor`
is a key at the same level as `resources`, so it seems `isset` is the
only option.

Logically I think that still works because if the value of
`$response['next_cursor']` is null, then this code should not execute.

Pull Request Pull Request #34:

Run Details

103 of 137 relevant lines covered (75.18%)

2.97 hits per line

enl / flysystem-cloudinary / 73 / 5
77%
master: 77%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 73.5 (EXECUTE_CS_CHECK=true EXECUTE_COVERAGE=true)

enl / flysystem-cloudinary / 73 / 5 77% master: 77%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 73.5 (EXECUTE_CS_CHECK=true EXECUTE_COVERAGE=true)

enl / flysystem-cloudinary / 73 / 5
77%
master: 77%

README BADGES
x