Posted by xjm

Following #1668820: Concept, base class, and interface for Configurables (e.g., node types, image styles, vocabularies, views, etc), core provides an interface and base class to standardize CRUD and storage handling for user-defined configuration data objects. Configurable data differs from plain configuration in that configurables must invoke and and respond to hooks. (See the original issue for details.)

Sub-issues

Note that all of the above issues should be added to the ConfigEntity change notice once it is complete.

Related issues

Abandoned conversions

Comments

xjm’s picture

Issue summary:View changes

Updated issue summary.

catch’s picture

ECK makes entity types into configuration, which would make them ConfigEntity objects in 8.x. We'd need to sort out the dependencies between content and config entities to do that (a config entity can't be a config entity and there's no real need to dynamically define config entities either, or at least not as much), but it'd be cool to have the capability in core.

catch’s picture

Issue summary:View changes

Updated issue summary.

andypost’s picture

andypost’s picture

andypost’s picture

Issue summary:View changes

Updated issue summary.

andypost’s picture

tim.plunkett’s picture

@andypost just update the issue summary, and stop editing your comment :)

tim.plunkett’s picture

Issue summary:View changes

Removed #916388: Convert menu links into entities because menu links will be content entities, not config.

podarok’s picture

#2 injected into summary

podarok’s picture

Issue summary:View changes
andypost’s picture

Issue summary:View changes

Added menu conversion issue

plach’s picture

Issue summary:View changes

Updated issue summary.

yched’s picture

One remark :

Unless I'm very mistaken, the CMI files created by both the "convert image styles to ConfigEntities" & "convert contact categories to ConfigEntities" do not hold any uuid entry.

The CMI files created there bypass ConfigStorageController and use raw config() calls directly - which seems reasonable, but also skips uuid creation.
Similarly, it seems we skip the creation of the manifest files.

Since it seems that's a very easy mistake to make (we made it ourselves in #1852966: Rework entity display settings around EntityDisplay config entity so far), this kind of calls for a _config_update_create_structure() helper function of some kind ?

tim.plunkett’s picture

Component:entity system» configuration entity system
tim.plunkett’s picture

Issue summary:View changes

Menu links is realted

tim.plunkett’s picture

Issue summary:View changes

Updated issue summary.

tim.plunkett’s picture

Issue summary:View changes

Updated issue summary.

catch’s picture

Issue summary:View changes

Adding issues.

catch’s picture

Issue summary:View changes

More issues.

catch’s picture

Issue summary:View changes

Updated issue summary.

tim.plunkett’s picture

Why aren't date formats a ConfigEntity? Looking at admin/config/regional/date-time, it really looks like they should be.

catch’s picture

That was #1571632: Convert regional settings to configuration system - did that go in before config entities?

tim.plunkett’s picture

That started way before ConfigEntity, but went in after. I think it was good that it went in as is, but it shouldn't be too hard to convert over now, and it fits the pattern perfectly.

catch’s picture

Bumping this so it's independently critical from #1775842: [meta] Convert all variables to state and/or config systems. It'd be good to close the variables issue when we remove variable_*() but CMI's not really done until core configuration is either deployable (or explicitly marked as content/in limbo like path aliases might end up being).

catch’s picture

Priority:Major» Critical
catch’s picture

Issue summary:View changes

Updated issue summary.

Gábor Hojtsy’s picture

Would converting actions make sense? (I think it would, not signing up for it :). Currently these are very custom DB stored thingies. In fact they are stored with their params as serialised blobs. Pretty scary. A side effect for this for D8MI is you can set a dsm() to go to the user or set an email action with a subject and body, but never translate it ever in any way. If only actions would be config entities, we could get rid of one more one-off core db stored thingie and get translation support for freeeeee!

Actions seem like a simple thing with aid, type (node, user, etc), callback, parameters (blob, AKA arbitrary data structure) and label. Currently action module has such code as:

<?php
function action_load($aid) {
  return
db_query("SELECT aid, type, callback, parameters, label FROM {actions} WHERE aid = :aid", array(':aid' => $aid))->fetchObject();
}
?>

Yeah. Could this just be an oversight that actions are not currently being worked on to become configurables? Is there some reason for them not to be ones?

Gábor Hojtsy’s picture

BTW two relevant issues for actions: #1788104: Convert actions to plugin sub-system and #1846172: Replace the actions API neither of which have been progressing lately. :/

Gábor Hojtsy’s picture

Issue summary:View changes

Updated issue summary.

heyrocker’s picture

I've added both those issues to the summary

andypost’s picture

Issue summary:View changes

Updated issue summary.

xjm’s picture

Issue summary:View changes

Removing myself from the author field so I can unfollow. --xjm

Berdir’s picture

Issue summary:View changes

Action has an issue and is already in the list, added reference to related rdf mapping issue

linclark’s picture

linclark’s picture

Issue summary:View changes

Added #1869600, which converts the RDF mapping.

linclark’s picture

Issue summary:View changes

Added #1778410, which moves namespaces to a config entity.

alexpott’s picture

Issue summary:View changes

Add date formats

tim.plunkett’s picture

Priority:Critical» Normal
tim.plunkett’s picture

Issue summary:View changes

Fix url

tim.plunkett’s picture

Issue summary:View changes
andypost’s picture

Status:Active» Fixed

Let's close this because only 1 left #1751274: Do not query user_roles directly

Status:Fixed» Closed (fixed)

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