api4 - Fix container cache/reload behavior
authorTim Otten <totten@civicrm.org>
Sun, 15 Sep 2019 18:19:06 +0000 (14:19 -0400)
committerColeman Watts <coleman@civicrm.org>
Tue, 17 Sep 2019 03:11:24 +0000 (23:11 -0400)
commitc1e9641deb0289aa9715d12097520f16a22707d0
tree40f85a39adc704dccc075633714f9d7dd14f077c
parent235e322db6bee7e3fc145322d73aa43b3c94e5c7
api4 - Fix container cache/reload behavior

In the extension's `tests/phpunit/bootstrap.php`, it forced the container to
*never* use caching. I suspect this was because of two problems:

1. APIv4 does a directory scan for services, but it didn't inform
   the container that this directory was important.

2. APIv4 registers additional services for a test environment, but the
   caching system didn't allow different caches for live-vs-test env's.
CRM/Api4/Services.php
CRM/Core/Config/Runtime.php