-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Draft Link/Button Ref #7905
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
base: develop
Are you sure you want to change the base?
Draft Link/Button Ref #7905
Conversation
marc-farre
left a comment
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.
@luke- 3 "reviews"
| } | ||
|
|
||
| $optionsRef = $this->getOptionsRef(); | ||
| $optionsRef = ArrayHelper::merge($this->getOptionsRef(), $options); |
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.
| /** | ||
| * @param string $color Hexadecimal, RGB, RGBA, HSL, HSLA | ||
| */ | ||
| public function cssBgColor(?string $color): static |
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.
I think we shouldn't encourage adding inline styling, especially for colors.
We already have ->style() for the rare case when we really need to force a color.
Instead, I would create a cssColor() method for the HtmlA class, which would only accept a BS color (success, etc.)
It would add one of these classes: https://getbootstrap.com/docs/5.3/helpers/colored-links/#link-colors
| /** | ||
| * @param string $color Hexadecimal, RGB, RGBA, HSL, HSLA | ||
| */ | ||
| public function cssTextColor(?string $color): static |
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.
Same here, I would remove it
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
developbranch, not themasterbranch if no hotfixFix #xxx[,#xxx], where "xxx" is the Github issue number)If adding a new feature, the PR's description includes:
Other information: