Use of slashes / quotes in config.yml about xsd2php HOT 6 CLOSED

I also ran into a problem when using forward slashes per the README.md. I realize that Windows paths use backslashes and Mac/Linux paths uses forward slashes. I think what is going on here is that namespaces are the problem, not filesystem paths.

When I first was reading, I was a bit confused as to why forward slashes would be used for defining PHP namespaces (but tried using them anyway). Using forward slashes would cause me to receive an error: "Unable to determine location to save PHP class ..." Changing to backslashes worked for me (I'm using Linux). Perhaps someone with Windows can confirm that namespaces with backslash work well for them too?

I think it is worth noting that the explanations of config.yml use backslashes, yet the sample config.yml uses forward slashes. Screenshot below...

from xsd2php.

/ are for mac Unix and Linux based systems
\ are for windows

Not sure if this should be documented

from xsd2php.

Was this the issue?

from xsd2php.

Quoting depends on yaml specifications.. and I'm not really deep into it

from xsd2php.

Not sure if this should be documented

Think this would be useful yes... I really had to puzzle a bit until I got it working and started doubting my configuration. A short comment can already help starting users:

destinations_php:
    #On Windows
    TestNs/MyApp: soap/src 
    #On Mac, Unix, Linux, etc
    TestNs\MyApp: soap/src 

Quoting depends on yaml specifications.. and I'm not really deep into it

Ok, well, my personal approach would be to leave as little to interpretation as possible, so either use it consistently (both for the key AND the value):

destinations_php:
    #On Windows
    'TestNs/MyApp': 'soap/src'
    #On Mac, Unix, Linux, etc
    'TestNs\MyApp': 'soap/src'

or not at all:

destinations_php:
    #On Windows
    TestNs/MyApp: soap/src 
    #On Mac, Unix, Linux, etc
    TestNs\MyApp: soap/src 

just my 2 cents, not big issues 😄

from xsd2php.

fixed with c93698f

from xsd2php.