Problem/Motivation

Part of #3575638: [META] Workspaces support for config entity types, we need to investigate what's need to support CRUD operations on field config entities in a workspace.

Proposed resolution

Allow field.field.* config objects (and field_config entity types) to be added/changed in a workspace.

Add test coverage for that, including entity view/form display changes.

Issue fork wse-3576534

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

amateescu created an issue. See original summary.

amateescu opened merge request !137

  • amateescu committed b4108c20 on 3.0.x 
    feat: #3576534 - wse_config: Investigate Workspace support for field...
amateescu’s picture

amateescu commented
Status: Active » Fixed

Merged!

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

amateescu’s picture

amateescu commented
Status: Fixed » Needs work

Still need to handle the field map :)

amateescu opened merge request !142

  • amateescu committed 0f85b768 on 3.0.x 
    feat: #3576534 wse_config - Additional test coverage for field_config...
amateescu’s picture

amateescu commented
Status: Needs work » Fixed

#3576744: Implement a workspace-aware key/value store and #3576850: Rewrite WseConfigDatabaseStorage: ConfigImporter-based publishing, delete/rename support, read path optimization handled all the really hard stuff for properly supporting field_config (and most other config entity types), what was left for this issue is only some additional test coverage, including a full functional test!

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

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