Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
configuration system
Priority:
Critical
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
9 May 2014 at 20:28 UTC
Updated:
29 Jul 2014 at 23:36 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
alexpottComment #2
berdirA few lines above it says that we don't do the invalid data tests?
Why are we even testing something like this? I noticed a lot of weird over-protective code in the CachedStorage that verified that the things we got back from the cache are valid and so on, we don't do that anywhere else...
that's like writing a test that inserts bogus values in the the node table and then tests if the entity storage can deal with that?
Comment #3
alexpottIn IRC @Berdir asked me if the PHPUnit test
Drupal\Tests\Core\Config\CachedStorageTestcovers this. I think we gain consistency since all classes that implement StorageInterface are tested with the same base test. So if we add further test coverage to this (as we do in #2262861: Add concept of collections to config storages) then CachedStorage automatically gets tested.Comment #4
gábor hojtsyTwo criticals are postponed on this (#2262861: Add concept of collections to config storages and #2224887: Language configuration overrides should have their own storage). The later one is even a beta blocker. So elevating to critical.
Looks to me like all changes proposed by Berdir have been fixed and the patch makes sense to me too :)
Comment #6
catchCommitted/pushed to 8.x, thanks!