-
Notifications
You must be signed in to change notification settings - Fork 3
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
Validating Magento 2 XML files #17
Comments
Your Can you try replacing <?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE catalog
PUBLIC "-//OASIS//DTD Entity Resolution XML Catalog V1.0//EN"
"http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd">
<catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog">
<uri
name="urn:magento:framework:Setup/Declaration/Schema/etc/schema.xsd"
uri="ROOT/vendor/Magento/framework/Setup/Declaration/Schema/etc/schema.xsd"/>
</catalog> It's been a while since I've worked with this stuff, though, so you might need to fiddle with that a bit. |
Thank you I got it working:
|
By the way, I think you could also do something along these lines: <rewriteURI uriStartString="urn:magento:framework:" rewritePrefix="file:///D:/path/to/installation/vendor/magento/framework/"/> I didn't test, though. |
The exact same statement worked great and saved tens of kilobytes! |
I'm nothing if not prudent when it comes to kilobytes. Glad to hear it works! |
I'm trying to make Exalt to work with Magento 2 xml files for validation. Its xml files could start with e.g.:
and that urn points to
schema.xsd
file in (starting from root directory):I have generated a catalog file named
misc.xml
with the built in Magento command which contains:and gave it to Exalt:
But Exalt throws error on not finding urn (
Failed to locate the main schema resource...
). Is there anyway to configure Exalt to understand the file path?Thanks
The text was updated successfully, but these errors were encountered: