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.
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
Consolidate accounts onboarding: Automatically preselect a Google Ads account when there is only one, as well as adjust the UI presentation #2608
Consolidate accounts onboarding: Automatically preselect a Google Ads account when there is only one, as well as adjust the UI presentation #2608
Changes from 6 commits
e7e6687
3b87196
5ab1b61
2fb0353
fd9f50a
a17ce78
6342061
f0e12a7
d575ba6
dc9b152
0eafa45
8c43ac6
004c9f6
08b16e0
f290352
d8f3ed9
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check warning on line 21 in js/src/components/ads-account-select-control/index.js
Codecov / codecov/patch
js/src/components/ads-account-select-control/index.js#L21
Check warning on line 32 in js/src/components/app-select-control/index.js
Codecov / codecov/patch
js/src/components/app-select-control/index.js#L32
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.
It's better to prefix the class names with
gla
org4w
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.
@ankitrox I see there are other parts where the
app-
prefix it used. For e.g most of thejs/src/components/app-*
components. Let's keep it as is.Examples: https://github.com/search?q=repo%3Awoocommerce%2Fgoogle-listings-and-ads+.app-+language%3ASCSS&type=code&l=SCSS
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.
Please check this comment from Eason.
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 understand what you're saying @ankitrox , but if you look at the current codebase, there are components which have the
gla-*
prefix class names and other specific components com which have theapp-*
prefix. Clearly there is a reason to why this is so. In this particular case, we are editing an existing component which already uses theapp-*
prefix, so I would be reluctant to change it. If you look atgoogle-listings-and-ads/js/src/components/shipping-rate-section/minimum-order-card/minimum-order-card.scss
Line 3 in 24044c5
app-*
. @eason9487 Can you shed some light please, about why we have 2 different CSS prefix, i.egla-*
andapp-*
? Thanks!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.
Early components often came with an
app-
prefix, but that is unnecessary and can be omitted for new components as it becomes a bit verbose.Regarding the CSS class naming, the main reason is to reduce the chance of CSS naming collisions.
app-
has significantly higher generality, sogla-
org4w-
would be more appropriate. The currentapp-
uses are almostly carry-over from earlier times, and newer code would be better to avoid using it as a prefix.If it involves changing existing code, it is not necessary to modify it. However, if the change (scope) is minor, it would be appreciated if it could be adjusted in the meantime.
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 clarification @eason9487 . I think that helps a lot. For the scope of this ticket, I suggest we keep it as is. We can have a separate ticket to adjust the class name. 👍
This file was deleted.