-
Notifications
You must be signed in to change notification settings - Fork 65
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
Less code isn't 100% valid #775
Comments
Hi @hostep. Thank you for your report. Please, add a comment to assign the issue:
|
One example about the You are trying to use the Lines 30 to 32 in f47c512
However, the definition of this class only exists on the frontend:
So this means that your code won't have an effect and should either be removed. Or - if you expect it to have an effect - to rework it so that it works as it's supposed to work. I didn't investigate the other cases, they might be similar ... |
Finally 😅 @engcom-Charlie or @engcom-Hotel: any idea why #777 isn't marked as merged? |
It's because commit 7d81e5c wasn't merged as well, can you guys please be a bit more careful when merging, so you don't miss stuff? Can somebody fix this please? Thanks! |
Preconditions (*)
Steps to reproduce (*)
npm install [email protected]
rm -R var/view_preprocessed/* pub/static/*; bin/magento setup:static-content:deploy -f --theme=Magento/backend en_US
node_modules/.bin/lessc -l var/view_preprocessed/pub/static/adminhtml/Magento/backend/en_US/css/styles.less
Expected result (*)
Actual result (*)
Discussion
The issues come from the page-builder module, when I don't have page builder installed with Magento 2.4.3, I don't get linting errors.
We've seen similar problems before in core Magento in the following tickets/PR's. Maybe reading those can help you figure out what exactly is wrong and how to fix these problems:
It would be great if the less code from this module has no linting errors.
Would also be super nice if Magento's static tests could include a check for this, so it doesn't get introduced in any other new modules that are created in the future
The text was updated successfully, but these errors were encountered: