Algo-Web / POData-Laravel

100%

master: 100%

LAST BUILD ON BRANCH OnlyLoadModelsOnBoot

branch: OnlyLoadModelsOnBoot

CHANGE BRANCH

x

Reset

• OnlyLoadModelsOnBoot
• 0.3.0
• 0.3.1
• 0.3.2
• 0.3.3
• 0.3.4
• 0.3.5
• 0.3.6
• MetadataImplementationStep
• RemixRegressionTests
• master
• metadataremix
• release-0.3.2
• revert-39-CleanuponFunctionCallExpression
• scrutinizer-patch-1
• scrutinizer-patch-2
• v0.2.0
• v0.2.1
• v0.2.2
• v0.2.3
• v0.2.4

Build # 572

Build Type

push

travis-ci

Committed by CyberiaResurrection

Commit Message

Properly handle abstract MetadataTrait-using models

By time the attempt is made to resolve an abstract model out of
the Laravel IoC container, it's both a subclass of Eloquent/Model
 AND using MetadataTrait.

Concrete classes resolve without a problem (see tests), but until now,
we never tested abstract classes that are both models and using ye olde
MetadataTrait.  Given (IIUC) that reflecting each and every class is
somewhat expensive, I decided to just charge ahead and only incur the
exception-throw overhead where there is a problem, rather than incurring
full reflection overhead on each class.

Run Details

2427 of 2427 relevant lines covered (100.0%)

140.87 hits per line