#1444620: Remove file signing from configuration system removed the file signing, but didn't remove the "Verified" from Drupal\Config class names.

Also, the class names could use some heavy clean-up.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

sun’s picture

Status: Active » Needs review
FileSize
8.99 KB
sun’s picture

FileSize
18.69 KB

Adjusted docs and renamed DrupalVerifiedStorageSQL into DatabaseStorage.

Status: Needs review » Needs work

The last submitted patch, config.classes.2.patch, failed testing.

sun’s picture

Status: Needs work » Needs review

FWIW, with this patch, core\lib\Drupal\Core\Config> dir /B yields:

AbstractStorage.php
ConfigException.php
DatabaseStorage.php
DrupalConfig.php
FileStorage.php
FileStorageException.php
FileStorageReadException.php
StorageInterface.php
sun’s picture

Odd. #2 should apply cleanly. Trying again.

sun’s picture

FileSize
13.72 KB

Briefly discussed the "Abstract" prefix in IRC. Removed it, as it's not strictly necessary and lines up Storage.php with StorageInterface.php:

ConfigException.php
DatabaseStorage.php
DrupalConfig.php
FileStorage.php
FileStorageException.php
FileStorageReadException.php
Storage.php
StorageInterface.php
yched’s picture

Denoting the abstract nature of the class within the class name is precious IMO.
Shouldn't be a blocker for this patch, but I wish we settled some convention regarding those "abstract" classes - opened #1567920: Naming standard for abstract/base classes about that.

gdd’s picture

Status: Needs review » Needs work

I don't have a strong feeling on this but based on the results of #1567920: Naming standard for abstract/base classes it appears that a standard has been essentially decided, so I'm putting this to CNW since it will undoubtedly need a reroll.

Otherwise I'm liking this a lot. Thanks sun.

sun’s picture

Status: Needs work » Needs review
FileSize
13.75 KB

Renamed Storage to StorageBase.

FWIW, this change is also available as a pull-able branch in cmi/config-classes-1567812-sun

(At some point, I'd like to have some clarity on what patches will be merged and which not, 'cos creating and maintaining feature branches involves a certain overhead.)

Status: Needs review » Needs work
Issue tags: -API clean-up, -Configuration system

The last submitted patch, config.classes.9.patch, failed testing.

sun’s picture

Status: Needs work » Needs review
Issue tags: +API clean-up, +Configuration system

#9: config.classes.9.patch queued for re-testing.

gdd’s picture

I haven't been maintaining feature branches for anything of late, although I was thinking about it for the rearchitecture issue since it is a more colossal change. I agree it is all pretty loose at this point and it would be nice to have some standards.

sun’s picture

Alright, "Drupal installation failed" was a testbot hiccup. Ready to fly?

gdd’s picture

Status: Needs review » Reviewed & tested by the community

Ayup

sun’s picture

#9: config.classes.9.patch queued for re-testing.

catch’s picture

Status: Reviewed & tested by the community » Fixed

We're over thresholds but internal stuff in cmi can't possibly conflict with any critical issues so I've gone ahead and committed this one.

Automatically closed -- issue fixed for 2 weeks with no activity.