Skip to content

[ReadMe] updated readMe file for ImportExport-LayeredNavigation modules #31809

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

Conversation

vlmed
Copy link
Contributor

@vlmed vlmed commented Jan 22, 2021

Description (*)

Update README.md file for modules:

  • Magento_ImportExport
  • Magento_Indexer
  • Magento_InstantPurchase
  • Magento_Integration
  • Magento_LayeredNavigation

Fixed Issues (if relevant)

  1. magento/devdocs README content for modules - work in M2 Code devdocs#4451: README content for modules - work in M2 Code

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds are green)

@m2-assistant
Copy link

m2-assistant bot commented Jan 22, 2021

Hi @vlmed. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

  • @magento give me test instance - deploy test instance based on PR changes
  • @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

  • @magento run all tests - run or re-run all required tests against the PR changes
  • @magento run <test-build(s)> - run or re-run specific test build(s)
    For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

  1. Database Compare
  2. Functional Tests CE
  3. Functional Tests EE,
  4. Functional Tests B2B
  5. Integration Tests
  6. Magento Health Index
  7. Sample Data Tests CE
  8. Sample Data Tests EE
  9. Sample Data Tests B2B
  10. Static Tests
  11. Unit Tests
  12. WebAPI Tests
  13. Semantic Version Checker

You can find more information about the builds here

ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review.

For more details, please, review the Magento Contributor Guide documentation.

⚠️ According to the Magento Contribution requirements, all Pull Requests must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of Pull Requests happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

@vlmed vlmed force-pushed the update_readme_import-export_layered-navigation branch from 06987ed to f7b6043 Compare January 22, 2021 15:44
@gabrieldagama gabrieldagama added the Priority: P2 A defect with this priority could have functionality issues which are not to expectations. label Jan 26, 2021
@vlmed vlmed force-pushed the update_readme_import-export_layered-navigation branch from f7b6043 to 496d9ff Compare February 3, 2021 12:29
@bgorski bgorski self-requested a review March 27, 2021 12:22
@bgorski bgorski self-assigned this Mar 27, 2021
@bgorski
Copy link
Contributor

bgorski commented Mar 27, 2021

@magento run all tests

Copy link
Contributor

@bgorski bgorski left a comment

Choose a reason for hiding this comment

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

@vlmed great job, you covered a lot of information here! I added some change requests, but it's clear that you put a lot of work in this already - thank you!


## Installation

The Magento_ImportExport module creates the following tables in the database:
Copy link
Contributor

Choose a reason for hiding this comment

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

Please add some information about the schema/column not being persistent (e.g. not having to be manually removed) when the module gets disabled and setup:upgrade is run.


### Public APIs

- `Magento\ImportExport\Api\Data\ExportInfoInterface`
Copy link
Contributor

Choose a reason for hiding this comment

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

The ExtendedExportInfoInterface interface is missing from the description. Please add it and describe in a little more detail both data interfaces so the readme provides clear enough info on what's the difference between them without having to look at the actual code.

- export data

- `\Magento\ImportExport\Api\ExportManagementInterface`:
- get export data
Copy link
Contributor

Choose a reason for hiding this comment

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

This is a bit misleading. "Export data" above and "get export data" here might suggest that this interface provides a repository-like getter, while in fact it provides logic for executing the actual export.

Magento_Indexer module is a base of Magento Indexing functionality.
# Magento_Indexer module

This module provides Magento Indexing functionality.
It allows:
Copy link
Contributor

Choose a reason for hiding this comment

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

Please improve wording on this. Like:

  1. "It allows to:" and the rest as is
  2. "It allows:" and the rest in present continuous (reading, representing, regenerating, viewing)


- `clean_cache_by_tags` event in the `\Magento\Indexer\Model\Indexer\CacheCleaner::cleanCache` method. Parameters:
- `object` is a `$this->cacheContext` object (`Magento\Framework\Indexer\CacheContext` class)
Copy link
Contributor

Choose a reason for hiding this comment

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

Imho this is a bit too detailed and dependent on the implementation. It's good to describe what class it is, but a description that this is the current cache context (instead of using an actual property name of the $this object) would suffice.


### Layouts

This module introduces the following layouts in the `view/frontend/layout` directory:
Copy link
Contributor

Choose a reason for hiding this comment

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

Please change wording from layouts to layout handles: https://devdocs.magento.com/guides/v2.4/frontend-dev-guide/layouts/layout-overview.html#layout-over-terms
Additionally, please include some basic info about how the module modifies layouts (things happening in the view/frontend/page_layout directory), but that's actually more suited for Additional Information as this section is about extension points.


### Layouts

This module introduces the following layouts in the `view/adminhtml/layout` directory:
Copy link
Contributor

Choose a reason for hiding this comment

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

### Layouts

This module introduces the following layouts in the `view/adminhtml/layout` directory:
Copy link
Contributor

Choose a reason for hiding this comment

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


### Layouts

This module introduces the following layouts in the `view/frontend/layout` directory:
Copy link
Contributor

Choose a reason for hiding this comment

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


## Additional information

More information can get at articles:
Copy link
Contributor

Choose a reason for hiding this comment

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

Please change the wording of this one to "More information can be found in:" or something similar to make this one grammatically correct

@bgorski bgorski added the Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests label Mar 27, 2021
@vlmed vlmed force-pushed the update_readme_import-export_layered-navigation branch from 496d9ff to 7f1dd3f Compare April 21, 2021 11:25
@vlmed
Copy link
Contributor Author

vlmed commented Apr 21, 2021

@magento run all tests

@vlmed
Copy link
Contributor Author

vlmed commented Apr 21, 2021

@bgorski Thank you for the review. I improved PR according to your recommendation

@magento-engcom-team
Copy link
Contributor

Hi @bgorski, thank you for the review.
ENGCOM-9075 has been created to process this Pull Request

@engcom-Foxtrot
Copy link
Contributor

@magento run Functional Tests EE

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

1 similar comment
@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@engcom-Foxtrot
Copy link
Contributor

@magento run Functional Tests EE

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@magento-engcom-team
Copy link
Contributor

Hi @Den4ik, thank you for the review.
ENGCOM-9075 has been created to process this Pull Request

@m2-assistant
Copy link

m2-assistant bot commented Jun 16, 2021

Hi @vlmed, 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 join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests Component: ImportExport Component: Indexer Component: InstantPurchase Component: Integration Component: LayeredNavigation Partner: Atwix Pull Request is created by partner Atwix partners-contribution Pull Request is created by Magento Partner Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: accept QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope Release Line: 2.4
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants