You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[How to create custom PageBuilder content type container]: docs/how-to-create-custom-content-type-container.md
22
-
<!--{% endcomment %}-->
23
-
24
-
<!-- {% raw %} -->
25
3
## Overview
26
4
27
5
Contributions to the Magento 2 codebase are done using the fork & pull model.
@@ -31,25 +9,23 @@ Contributions can take the form of new components/features, changes to existing
31
9
32
10
The Magento 2 development team will review all issues and contributions submitted by the community of developers in the first in, first out order. During the review we might require clarifications from the contributor. If there is no response from the contributor for two weeks, the issue is closed.
33
11
34
-
35
12
## Contribution requirements
36
13
37
14
1. Contributions must adhere to [Magento coding standards](http://devdocs.magento.com/guides/v2.0/coding-standards/bk-coding-standards.html).
38
15
2. Pull requests (PRs) must be accompanied by a meaningful description of their purpose. Comprehensive descriptions increase the chances of a pull request to be merged quickly and without additional clarification requests.
39
16
3. Commits must be accompanied by meaningful commit messages.
40
17
4. PRs which include bug fixing, must be accompanied with step-by-step description of how to reproduce the bug.
41
-
3. PRs which include new logic or new features must be submitted along with:
42
-
* Unit/integration test coverage where applicable.
43
-
* Updated documentation in the module directory `app/code/PageBuilder/docs`.
44
-
4. For large features or changes, please [open an issue](https://github.com/magento/magento2/issues) and discuss first. This may prevent duplicate or unnecessary effort, and it may gain you some additional contributors.
45
-
5. All automated tests are passed successfully locally. After PR submitted Magento team will run builds on continuous integration environment.
18
+
5. PRs which include new logic or new features must be submitted along with:
19
+
* Unit/integration test coverage where applicable.
20
+
* Updated documentation in the `docs` directory at the root level.
21
+
6. For large features or changes, please [open an issue](https://github.com/magento/magento2/issues) and discuss first. This may prevent duplicate or unnecessary effort, and it may gain you some additional contributors.
22
+
7. All automated tests are passed successfully locally. After PR submitted Magento team will run builds on continuous integration environment.
46
23
47
24
## Contribution process
48
25
49
26
If you are a new GitHub user, we recommend that you create your own [free github account](https://github.com/signup/free). By doing that, you will be able to collaborate with the Magento 2 development team, “fork” the Magento 2 project and be able to easily send “pull requests”.
50
27
51
-
1. Search current [listed issues](https://github.com/magento/magento2-page-builder/issues) on GitHub (open or closed) and [list of known issues](docs/roadmap.md#Known Issues) on our roadmap for similar proposals of intended contribution before starting work on a new contribution.
52
-
2. Please contact us in Slack chanel if you want to work on issue from [list of known issues](docs/roadmap.md#Known Issues).
28
+
1. Search current [listed issues](https://github.com/magento/magento2-page-builder/issues) on GitHub (open or closed) before starting work on a new contribution.
53
29
2. Review the [Contributor License Agreement](https://magento.com/legaldocuments/mca) if this is your first time contributing.
54
30
3. Create and test your work.
55
31
4. Fork the Magento 2 repository according to [Fork a repository instructions](http://devdocs.magento.com/guides/v2.0/contributor-guide/contributing.html#fork) and when you are ready to send us a pull request – follow [Create a pull request instructions](http://devdocs.magento.com/guides/v2.0/contributor-guide/contributing.html#pull_request). Instructions written for `https://github.com/magento/magento2` repository, but they also apply to `https://github.com/magento/magento2-page-builder`.
@@ -59,5 +35,3 @@ If you are a new GitHub user, we recommend that you create your own [free github
59
35
60
36
Please note that this project is released with a Contributor Code of Conduct. We expect you to agree to its terms when participating in this project.
61
37
The full text is available in the repository [Wiki](https://github.com/magento/magento2/wiki/Magento-Code-of-Conduct).
<elementname="showOverlay"type="button"selector="(//div[contains(@class,'pagebuilder-banner') and @data-element='main'])[{{arg1}}][@data-show-overlay='{{arg2}}']"parameterized="true"/>
101
102
<elementname="overlayColorAndTransparency"type="button"selector="(//div[contains(@class,'pagebuilder-banner') and @data-element='main'])[{{arg1}}]//div[@data-element='overlay'][contains(@style,'background-color: rgba({{arg2}}, {{arg3}});')]"parameterized="true"/>
102
103
<elementname="transparentOverlay"type="button"selector="(//div[contains(@class,'pagebuilder-banner') and @data-element='main'])[{{arg1}}]//div[@data-element='overlay'][contains(@style,'background-color: transparent;')]"parameterized="true"/>
104
+
<elementname="inlineWYSIWYGEditorWithTag"type="text"selector="(//div[contains(@class,'pagebuilder-banner') and @data-element='main'])[{{arg1}}]//div[contains(@class,'inline-wysiwyg')]//{{arg2}}"parameterized="true"/>
103
105
<!-- Advanced Configuration -->
104
106
<elementname="alignment"type="text"selector="(//div[contains(@class,'pagebuilder-banner') and @data-element='main'])[{{arg1}}]//div[@data-element='wrapper'][contains(@style,'text-align: {{arg2}};')]"parameterized="true"/>
105
107
<elementname="noAlignment"type="text"selector="(//div[contains(@class,'pagebuilder-banner') and @data-element='main'])[{{arg1}}]//div[@data-element='wrapper'][not(contains(@style,'text-align:'))]"parameterized="true"/>
<elementname="overlayColorAndTransparency"type="button"selector="(//div[@data-role='slide'])[{{arg1}}]//div[@data-element='overlay' or contains(@class,'pagebuilder-overlay')][contains(@style,'background-color: rgba({{arg2}}, {{arg3}});')]"parameterized="true"/>
161
162
<elementname="transparentOverlay"type="button"selector="(//div[@data-role='slide'])[{{arg1}}]//div[@data-element='overlay' or contains(@class,'pagebuilder-overlay')][contains(@style,'background-color: transparent;')]"parameterized="true"/>
Copy file name to clipboardExpand all lines: app/code/Magento/PageBuilder/Test/Mftf/Section/PageBuilderTextSection.xml
+2Lines changed: 2 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -27,6 +27,7 @@
27
27
<elementname="textInImportantStyle"type="text"selector="(//div[contains(@class,'pagebuilder-text')])[{{arg1}}]//div[contains(normalize-space(@class), 'cms-content-important') and text()='{{arg2}}']"parameterized="true"/>
0 commit comments