LBF carries a several attributes that it only need to init CP object, including $secret that might be confusing to reader what the secret is about. Also, LBF should not be really coupled to CP, at least not this much. Most stuff happen via calling CP functions passed by $lb object. Some callers of LBF methods also don't need LBF really, they need the CP object (e.g. ::disableChronologyProtection()) which in turn we can make ChronologyProtector a dedicated service (it only needs BagOStuff and secret from the LBF configuration, the rest are CLI mode or logger) and call those separately and slowly just inject it to LBF instead. This patch has already reduced the size of LBF by 10%. Bug: T275713 Change-Id: If5e34a372030238093b66c292a02d11e5933ff88 |
||
|---|---|---|
| .. | ||
| api-testing | ||
| common | ||
| parser | ||
| phpunit | ||
| qunit | ||
| selenium | ||
| .htaccess | ||