Problem/Motivation

Currently, the values of the classes associated with a utility class are defined directly, which could be problematic if in an existing site, you want to change the structure of theming or classes or you want to use another base theme that requires different utilities.

Proposed resolution

  1. Add an identifier field to each value of a utility class to store the value of the class selection (instead suffix value that may require adjustments), also use that value as saved value instead the current one.
  2. Add description to "Identifier" fields in form to inform that changing that value produce any utility usement loss (to both fields, utility & new for each value).
  3. Avoid any related regression to current installation sites (update or TBD).

Issue fork vlsuite-3361220

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:

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

albeorte created an issue. See original summary.

CRZDEV’s picture

Issue summary: View changes
CRZDEV’s picture

Issue summary: View changes

  • albeorte committed 052d037f on 1.0.x
    Issue #3361220: Replace utility values configurations with identifiers
    

  • albeorte committed 080c00fc on 1.0.x
    Issue #3361220: Adjust initial configuration with value identifier base
    

  • albeorte committed aa67f96e on 1.0.x
    Issue #3361220: Add classes to previewer with identifier structure
    

  • albeorte committed 14ce6bf5 on 1.0.x
    Issue #3361220: Add description to identifier fields
    

  • albeorte committed 001632f1 on 1.0.x
    Issue #3361220: Add identifier to utility classes values
    
CRZDEV’s picture

Current progress integrated, other update pending

  • albeorte committed e283489f on 1.0.x
    Issue #3361220: Refactor utility value identifiers names
    

tunic’s picture

Updating credit info per MR review by CRZDEV.

Eduardo Morales Alberti made their first commit to this issue’s fork.

CRZDEV’s picture

Component utilities initial version ready, pending:
- "Discard changes" seems needed but it applies?! (see drush cex, pending delete section storage loaded by context at display level)
- Update for content
- Update for section library
- Move updates to correct module
- Make some testing

CRZDEV’s picture

Section storage ready for displays ("Discard changes" seems needed but it applies?! (see drush cex, pending delete section storage loaded by context at display level)), pending:
- Update for content
- Update for section library
- Move updates to correct module
- Make some testing

CRZDEV’s picture

Assigned: albeorte » CRZDEV

  • CRZDEV committed dfb41222 on 1.0.x authored by albeorte
    Issue #3361220 by CRZDEV, albeorte, Eduardo Morales Alberti: Use...
CRZDEV’s picture

Status: Active » Fixed

Update ready & checked into quite complex site at display config level, content & library.

Status: Fixed » Closed (fixed)

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