You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: