Skip to content

system_file.xsd - better code highlight when using URN schemas #39867

New issue

Have a question about this project? No Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “No 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? No Sign in to your account

Open
wants to merge 3 commits into
base: 2.4-develop
Choose a base branch
from

Conversation

jakwinkler
Copy link

Description (*)

Fixes XML schema definitions in phpstorm, from this:

image

to this:
image

Related Pull Requests

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)
  • README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
  • All automated tests passed successfully (all builds are green)

Copy link

m2-assistant bot commented Apr 26, 2025

Hi @jakwinkler. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.
❗ 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
ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.


For more details, review the Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.

@jakwinkler
Copy link
Author

@magento run all tests

1 similar comment
@jakwinkler
Copy link
Author

@magento run all tests

@jakwinkler
Copy link
Author

@magento run all tests

@hostep
Copy link
Contributor

hostep commented Apr 28, 2025

Thanks @jakwinkler, but it looks like we already have a PR that tries to fix the same thing over here: #39675

@engcom-Hotel
Copy link
Contributor

Thanks @hostep for highlighting the other PR which fixes the same issues.

@jakwinkler please have a look at the other PR, till the time moving this PR on hold.

@jakwinkler
Copy link
Author

jakwinkler commented Apr 29, 2025

@hostep that was my initial idea as well, but some comments use a model to generate a comment and your solution won't work if you have some Adobe Commerce module installed.
Check my commit history and you'll see that I've tried to use same approach but it will fail on this code

<comment model="Magento\Securitytxt\Model\Config\Signature"/>

My PR covers all scenarios :-)

@hostep
Copy link
Contributor

hostep commented Apr 29, 2025

Nice! Good to hear you did some research. Then I agree we should proceed with this PR and close the other one.

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

Successfully merging this pull request may close these issues.

3 participants