-
-
Notifications
You must be signed in to change notification settings - Fork 825
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
Give the custom css file a 'name' to make it easier to manipulate in hook_civicrm_alterBundle() #20278
Merged
Merged
Give the custom css file a 'name' to make it easier to manipulate in hook_civicrm_alterBundle() #20278
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like a very good idea. A small suggestion though.
Do we need the
:css
thingy? How about just making itcivicrm:custom.css
.Its not a huge deal, but
civicrm:css/custom.css
kind of makes it looks like a URL. Whencivicrm:custom.css
looks more of an identifier.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah yes ... what's in a name??
Resources added via
addStyleFile()
have a default name combining the extension name and the relative path so the other resources added bycreateStyleBundle()
arecivicrm:css/civicrm.css
andcivicrm:css/crm-i.css
. So following that pattern of names I went withcivicrm:css/custom.css
. However,civicrm
- but it is added by core.css
- but is quite likely to be[civicrm.files]/css
custom.css
- but is a common optionProviding the name is unique I don't think it matters much. The purpose is to let people target that custom css file, whatever it's actual filename or path. I did consider
civicrm:custom.css
but thought the omission of thecss/
part might cause more question since the name then does not follow the pattern of the other names in the bundle.Happy to change the name if there's consensus on a better one.
And while you're all thinking about this, perhaps you could also comment on https://lab.civicrm.org/dev/core/-/issues/2460 which led to this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the explanation. It makes sense, no need to change in that case.