-
-
Notifications
You must be signed in to change notification settings - Fork 21.9k
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
Add an XML schema for documentation #35679
Conversation
Based on a very cursory web search, It seems so, with a couple of variations:
Simplest option seems to be: <xs:complexType/> |
3dfe235
to
05f3d5b
Compare
05f3d5b
to
ae88586
Compare
I updated the pull request to add the XML schema mention in the root tag when using |
I support using existing xml tools to validate our xml variation. Xml validators allows tools to check our xml docs. We didn't need validators at first, but with the growth of Godot Engine scope and scale tool validators help. |
I don't see code added to |
I forgot to readd that part while remaking this PR from scratch, and I no longer have the original code around 🙁 |
Some of your old commits referenced above in force push notifications haven't been GC'ed yet: Could use |
495869a
to
b3e6be4
Compare
Some XMLs have the wrong path: https://github.com/godotengine/godot/runs/5187484781?check_suite_focus=true |
b3e6be4
to
cfa7080
Compare
Fixed. I suppose this happens because I ran |
There's a style issue in the |
f3ada17
to
cdbb9af
Compare
This makes it easier to spot syntax errors when editing the class reference. The schema is referenced locally so validation can still work offline. Each class XML's schema conformance is also checked on GitHub Actions.
cdbb9af
to
b68dd2e
Compare
We could make the CI output quieter by using
|
Thanks! |
master
version of #59213.This makes it easier to spot syntax errors when editing the class reference. The schema is referenced locally so validation can still work offline.
Tested with the vscode-xml Visual Studio Code add-on.