Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Card embed block names #120

Open
cavasinf opened this issue Oct 4, 2022 · 5 comments
Open

Card embed block names #120

cavasinf opened this issue Oct 4, 2022 · 5 comments
Labels
BC Break This will cause BC Break Feature Feature requested Status: Reviewed Has staff reply/investigation
Milestone

Comments

@cavasinf
Copy link
Collaborator

cavasinf commented Oct 4, 2022

Big BC BREAK but we should rename blocks inside card embed.

<div class="card-header{% if block('box_header_class') is defined %} {{ block('box_header_class') }}{% endif %}">

They are called box_xxxxx as a remnant of AdminLTE. And classes card-xxxx
We should stick to Bootstrap and/or Tabler name convention and use card_xxxx instead.

WDYT ?

@cavasinf cavasinf added Invalid This doesn't seem right Status: Needs Review Not under investigation labels Oct 4, 2022
@cavasinf cavasinf mentioned this issue Oct 4, 2022
5 tasks
@kevinpapst
Copy link
Owner

Yeah, I think that is true: but I hate the idea, considering in how many files I use these block names ^^
But we should write a wrapper that is able to handle that name change for existing installations...

@cavasinf
Copy link
Collaborator Author

cavasinf commented Oct 4, 2022

A "replace in files" CTRL + SHIFT + R from " box_" to " card_" (with a space at the beginning) should be enough? 😄

102+ ref on my side 😭
image

But we should write a wrapper that is able to handle that name change for existing installations...

And AdminLTEBundle Migration..

@cavasinf cavasinf added this to the 1.1 milestone Oct 4, 2022
@cavasinf cavasinf added Status: Reviewed Has staff reply/investigation Feature Feature requested and removed Invalid This doesn't seem right Status: Needs Review Not under investigation labels Oct 4, 2022
@kevinpapst
Copy link
Owner

Likely yes, but: my software supports plugins and there are many, which are not under my control... but they will have to adapt to the new theme anyway 😁 so good to go from my side.

@kevinpapst kevinpapst modified the milestones: 1.1, 1.0 Oct 4, 2022
@kevinpapst
Copy link
Owner

Changed the milestone, because this has to be done BEFORE the first "real" release.

@wucherpfennig
Copy link
Contributor

Please just make sure to notify me before I update ;-) well... I will find out anyway ^^

@cavasinf cavasinf added the BC Break This will cause BC Break label Mar 31, 2023
@kevinpapst kevinpapst modified the milestones: 1.0, 2.0 Sep 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BC Break This will cause BC Break Feature Feature requested Status: Reviewed Has staff reply/investigation
Projects
None yet
Development

No branches or pull requests

3 participants