Add the name of the component before utility_classes in all components to avoid inheriting utility_classes from parent components

Created on 27 February 2025, about 1 month ago

Problem/Motivation

Steps to reproduce

Proposed resolution

Remaining tasks

  • ✅ File an issue about this project
  • ❌ Addition/Change/Update/Fix to this project
  • ❌ Testing to ensure no regression
  • ➖ Automated unit/functional testing coverage
  • ➖ Developer Documentation support on feature change/addition
  • ➖ User Guide Documentation support on feature change/addition
  • ➖ UX/UI designer responsibilities
  • ➖ Accessibility and Readability
  • ❌ Code review from 1 Varbase core team member
  • ❌ Full testing and approval
  • ❌ Credit contributors
  • ❌ Review with the product owner
  • ❌ Update Release Notes and Update Helper on new feature change/addition
  • ❌ Release

Varbase update type

  • ✅ No Update
  • ➖ Optional Update
  • ➖ Forced Update
  • ➖ Forced Update if Unchanged

User interface changes

  • N/A

API changes

  • N/A

Data model changes

  • N/A

Release notes snippet

  • N/A
Feature request
Status

Active

Version

3.0

Component

Code

Created by

🇯🇴Jordan alaa abbad

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @alaa abbad
  • 🇯🇴Jordan Rajab Natshah Jordan

    Thank you so much, Alaa, for reporting and suggesting this important change of direction.

    I completely agree with it. We're moving forward with UI Patterns ~2.0, fully utilizing View modes and fields. All nesting issues related to passing utility_classes will be properly handled.

    Updated the summary of the issue with points from our internal dissociation

  • 🇯🇴Jordan Rajab Natshah Jordan

    Thanks, Alaa Abbad, for suggesting and filing the issue.

    Approved to move foreword with this major change by Razem, to remove any issues with nesting.

Production build 0.71.5 2024