typhonius / acquia-php-sdk-v2

99%

master: 99%

LAST BUILD ON BRANCH catch-api-errors

branch: catch-api-errors

CHANGE BRANCH

x

Reset

• catch-api-errors
• 1.0.0
• 1.0.1
• 1.0.4
• 1.1
• 1.1.0
• 1.1.1
• 1.1.2
• 2.0
• 2.0.0
• 2.0.1
• 2.0.10
• 2.0.11
• 2.0.12
• 2.0.13
• 2.0.14
• 2.0.2
• 2.0.3
• 2.0.4
• 2.0.5
• 2.0.6
• 2.0.7
• 2.0.8
• 2.0.9
• 64-delete-database-backup
• 7.4
• add-account-method
• add-getAdmin
• add-links-to-operations
• add-user-agent
• alter-guzzle-options
• better-api-errors
• change-role-fixture
• delete-cd-environment
• download-db
• drop-phpcs-version
• drop-phpcs-version-and-unused-deps
• fix-user-agent-string-application
• funding
• get-user
• getEnvironment-fix
• github-actions
• hotfix-post-options
• inheritdoc
• issue-templates
• logstream
• master
• move-options
• new-coveralls-path
• notifications
• php73
• phpcs-to-dev
• phpmd
• tests
• token-expiration
• truncateDB
• try-phpdbg
• typhonius-funding
• update-dependencies
• update-phpcs

Build # 297

Build Type

push

travis-ci

Committed by typhonius

Commit Message

Adds final test case and resends the Exception.

The reason I have chosen to throw an exception
instead of catching the exception and printing
a message is twofold.

Firstly, we cannot test the use of an exit()
or die() that would be required to catch the
error and present a message alerting the user
of the issue.

Secondly, by handling the error, it prevents
consumming libraries from easily detecting an
error has been thown and handling it gracefully.

Both of these reasons have lead me to determining
that Exceptions should be handled in code by
consuming libraries. I'll document this on the
README so users can handle the exceptions if they
wish. I'll also have to use this in Acquia Cli
and Acquia Logstream. I don't catch errors in
these at all right now so it would be an
enhancement!

Run Details

1 of 1 new or added line in 1 file covered. (100.0%)

790 of 802 relevant lines covered (98.5%)

13.23 hits per line