-
Notifications
You must be signed in to change notification settings - Fork 64
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
[WIP] #558 #7 Developer can style content types output differently per viewport - fix broken tests #627
[WIP] #558 #7 Developer can style content types output differently per viewport - fix broken tests #627
Conversation
@lbvaimo unfortunately, only members of the maintainers team are allowed to assign developers to the pull request |
@lbvaimo unfortunately, only members of the maintainers team are allowed to assign developers to the pull request |
1 similar comment
@lbvaimo unfortunately, only members of the maintainers team are allowed to assign developers to the pull request |
…onents are always nested in a Contained component - Fixing MFTF CR feedback
…onents are always nested in a Contained component - Fixing filename
…lder into imported-magento-magento2-page-builder-631
…gento2-page-builder-631 [Imported] MC-35402: [Page Builder] New top-level Full-Width and Full-Bleed comp�
…ew groups, changed name in Pascal caps format
@magento run Functional Tests EE |
- were updated ALL deprecated action groups
@magento run Functional Tests EE |
1 similar comment
@magento run Functional Tests EE |
- fixed bugs in test generation and changed all references on groups
@magento run Functional Tests EE |
1 similar comment
@magento run Functional Tests EE |
- I changed references in PB-EE in PR 173 - I made refactoring follow groups: ValidateAdvancedConfigurationWithAlignmentActionGroup ValidateAdvancedConfigurationWithBorderColorActionGroup ValidateAdvancedConfigurationWithCssClassesActionGroup ValidateAdvancedConfigurationWithNoAlignmentActionGroup ValidateAdvancedConfigurationWithNoAlignmentEmptyBorderRadiusActionGroup ValidateAdvancedConfigurationWithNoBorderActionGroup ValidateAdvancedConfigurationWithNoBorderRadiusActionGroup
@magento run Functional Tests EE |
…rt - Banner Content Type Mftf fixes
…magento2-page-builder into 558_7_content-type-style-attribute-removal
@magento run Functional Tests EE |
…rt - Banner Content Type Mftf fixes
- I made refactoring follow groups: ValidateAdvancedConfigurationWithNoBorderWidthActionGroup ValidateAdvancedConfigurationWithNoMarginsActionGroup ValidateAdvancedConfigurationWithNoPaddingActionGroup
…te-removal' into 558_7_content-type-style-attribute-removal
@magento run Functional Tests EE |
- I made refactoring follow groups: ValidateAdvancedConfigurationWithNoMarginsActionGroup ValidateBackgroundConfigurationWithNoImageActionGroup
@magento run Functional Tests EE |
Story
As a developer I want to easily create themes and customizations to existing Page Builder content types to enable me align their visual output with my desired theme
Business Value
ability to style content with CSS classes not using !important
Acceptance Criteria
Technical Vision
Story
#558
Related Pull Requests
https://github.com/magento/magento2-page-builder-ee/pull/173
Checklist