While using this amazing tool I noticed that Comments are parsed from xsd to php without escaping slashes ( / ).
Thus resulting in a broken class (which can easily be fixed by escaping the slash with a backslash ( \ ) ).
I have shortened the commentary and replaced it with [...] to prevent unnecessary bloating.
I assume a simple search and replace could be all that is needed to prevent this in the future?
While using this amazing tool I noticed that Comments are parsed from xsd to php without escaping slashes ( / ). Thus resulting in a broken class (which can easily be fixed by escaping the slash with a backslash ( \ ) ).
The following XSD:
Results in the following PHP:
It could be fixable by just adding a backslash before the slash