Skip to content
This repository has been archived by the owner on Nov 19, 2024. It is now read-only.

Adding cli commands in custom payment method page #6577

Merged
merged 3 commits into from
Feb 11, 2020

Conversation

VinothKumar361
Copy link
Contributor

Purpose of this pull request

Adding cli commands in custom payment method page

Affected DevDocs pages

@devops-devdocs
Copy link
Collaborator

An admin must run tests on this PR before it can be merged.

1 similar comment
@devops-devdocs
Copy link
Collaborator

An admin must run tests on this PR before it can be merged.

@dshevtsov dshevtsov requested review from a team and removed request for dshevtsov February 6, 2020 18:02
@@ -308,5 +308,24 @@ In your custom module directory, create a new `<your_module_dir>/view/frontend/l
</body>
</page>
```
## Step 5:Run the CLI Commands {#compile-code-deploy-contents-and-clean-the-cache}
Copy link
Contributor

@rogyar rogyar Feb 7, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @VinothKumar361. Thank you for your collaboration.

I'm not sure we need this information trough the documentation. The DevDocs is a resource with the Magento development-related documentation. The target audience is Magento developers.

If you are a Magento developer, you are supposed to know the very basic development routine like cache cleaning, running your development environment, using IDE/browser before creating working solutions. So, posting this info over and over again on all pages (it applies to most of the code change operations though) might not be as useful as we want it to see.

Also, if we are talking about Magento development, the developer's environment is supposed to be in the developer mode which does not require DI compilation and static content deployment. On production environments, the mentioned operations should be a part of the deployment process.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You make a good point, Rogyar. There have been a few PRs adding this same info to other topics. I would rather lean on the side of providing more information than necessary, if it can prevent confusion to users. Good feedback.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From the other hand, providing more information than necessary leads to future search and maintenance issues.
If the information is relevant and must be present in several topics, consider using the {% include %} functionality to follow the docs-like DRY principle.

@@ -308,5 +308,24 @@ In your custom module directory, create a new `<your_module_dir>/view/frontend/l
</body>
</page>
```
## Step 5:Run the CLI Commands {#compile-code-deploy-contents-and-clean-the-cache}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You make a good point, Rogyar. There have been a few PRs adding this same info to other topics. I would rather lean on the side of providing more information than necessary, if it can prevent confusion to users. Good feedback.

@dobooth dobooth added 2.3.x Magento 2.3 related changes Technical Updates to the code or processes that alter the technical content of the doc labels Feb 11, 2020
@dobooth
Copy link
Contributor

dobooth commented Feb 11, 2020

running tests

@dobooth dobooth merged commit 319f64a into magento:master Feb 11, 2020
@ghost
Copy link

ghost commented Feb 11, 2020

Hi @VinothKumar361, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
2.3.x Magento 2.3 related changes Partner: Ziffity partners-contribution PR created by Magento partner Technical Updates to the code or processes that alter the technical content of the doc
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants