Skip to content

[0.12] Refactor Attribute Lists#591

Draft
Severino wants to merge 5 commits into0.12-feat-required-attributesfrom
0.12-feat-required-attributes-components
Draft

[0.12] Refactor Attribute Lists#591
Severino wants to merge 5 commits into0.12-feat-required-attributesfrom
0.12-feat-required-attributes-components

Conversation

@Severino
Copy link
Contributor

A big priority of mine is to make things more manageable when we touch them:
Smaller, reusable components and externalizing business logic.

Therefore, I'm currently refactoring the AttributeControls and move them out of the AttributeList (which very bloated, as it supports functionality of every place it is implemented in).

  • simplified hover logic
  • added ghost-class to visually separate dragged element
  • added 'before-container' slot on attribute-list
  • added the 'fab-button-list'
  • added 'AttributeListControls' and 'EntityAttributeListControls' which are used directly on the DataModel and DataModelDetailView

certainty,
handleSelectionUpdate,
additionalRowClasses,
addModerationStateClasses,
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I sorted the return alphabetically.

/>
</button>
</div>
<FabButtonList
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I replaced this directly with the fabbuttonlist component. (As it also served as template for that component)

item-key="id"
class="attribute-list-container align-content-start"
:class="classes"
ghost-class="vue-draggable-ghost"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wanted to use multiple bootstrap classes, but it's not possible. See in _style.scss
which then uses bootstrap variables.

@v1r0x
Copy link
Member

v1r0x commented Oct 31, 2025

A big priority of mine is to make things more manageable when we touch them:
Smaller, reusable components and externalizing business logic.

I get the idea, but I didn't really touch that much of the code and it was working fine.
This (currently) only leads to a lot more PRs and PRs to PRs to PRs, cherrypicks and rebases that break something almost any time.
We should either focus on a refactor release or a feature release.
We have already a lot of PRs that are not reviewed (and maybe never looked at at all) or that outdated, that all the work has to be done again. Also a lot of branches are outdated that require a lot of manual cherrypicking/rebasing (hopefully without breaking something again).

With this it makes no sense to me to implement any feature/logic, because it takes weeks or even months for another PR to get reviewed and merged. Then I have to fiddle around to merge my code into a completely new logic...

@Severino Severino changed the title [0.12] feat required attributes components (WIP) [0.12] Refactor Attribute Lists Nov 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants