Skip to content
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

[UCT] Add support for the Magento 2 configuration files, such as di.xml, system.xml, etc #1030

Closed
bohdan-harniuk opened this issue Mar 15, 2022 · 1 comment · Fixed by #1038

Comments

@bohdan-harniuk
Copy link
Collaborator

bohdan-harniuk commented Mar 15, 2022

Is your feature request related to a problem? Please describe.

The internal UCT analyses *.php and *.phtml files in the Magento 2 modules and themes. We should add support for the Magento 2 configuration files. All configuration files, that can contain class/interface/constant FQN should be covered by the UCT feature.

Describe the solution you'd like (*)

Next Magento 2 configuration files should be analysed:

  • di.xml
  • system.xml
  • events.xml
  • extension_attributes.xml
  • webapi.xml
  • communication.xml
  • queue_consumer.xml
  • crontab.xml
  • indexer.xml
  • mview.xml
  • product_types.xml
  • widget.xml
  • view/(base|frontend|adminhtml)/layout/*.xml
  • view/(base|frontend|adminhtml)/ui_component/*.xml
  • product_options.xml
  • export.xml
  • import.xml
  • analytics.xml
  • reports.xml
  • pdf.xml
  • cache.xml
  • validation.xml
  • queue.xml

Describe alternatives you've considered

N/A. But any ideas will be appreciated.

Additional context

Mainline branch: 4.3.0-develop

@m2-assistant
Copy link

m2-assistant bot commented Mar 15, 2022

Hi @bohdan-harniuk. Thank you for your report.
To speed up processing of this issue, make sure that you provided sufficient information.

Add a comment to assign the issue: @magento I am working on this


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant