[Misc] Improve consistency of global LESS variable declaration in Flamingo #3663
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.
Jira URL
None, quality change only.
Changes
Description
@loginFormMaxWidth
to@login-form-max-width
@border-width
from the override section to the XWiki specific section (it was incorrectly set here...)to override
isoverridden
:)Clarifications
xwiki-platform/xwiki-platform-core/xwiki-platform-flamingo/xwiki-platform-flamingo-skin/xwiki-platform-flamingo-skin-resources/src/main/resources/flamingo/less/style.less.vm
Line 27 in 7683202
@loginFormMaxWidth
was renamed because it did not respect our naming convention (strictly speaking we don't have one for naming LESS variables, but we have one for HTML/CSS classes and bootstrap had one that we followed for pretty much all other variables). This is technically a backward compatibility break, but the name and use of this variable is so niche that I doubt anyone used it in a customization...Screenshots & Video
None, code quality changes only.
Executed Tests
Passed
mvn clean install -f xwiki-platform-core/xwiki-platform-flamingo/xwiki-platform-flamingo-skin -Pquality,docker
without an issue.I conducted a quick manual test by moving the changes related to font size on my local instance. After a reset of the instance and its LESS cache, the titles still had the right font size 👍 .
Expected merging strategy