Syncano-cli call throws error on grouped endpoint

[chinazor-allen]

s call throws error message on grouped endpoint (e.g s call stripe/charge/createcharges/) when run on command line, but, endpoint works fine in postman and browers.

In defining the grouped endpoint, the following steps were taken:

• Create a charge folder in src folder
• create charge related script file (e.g. createCharges.js, retrieveCharges.js, e.t.c.) in src/charge folder
• Define endpoint in socket.yml file as shown below (N/B: without the file path):

Error message:

No such endpoint on the server! Make sure you have synced your socket.

[mkucharz]

@Andela-callen @adamwardecki I think actually that kind of format of the endpoint name can create lot more of such problems and for now should be forbidden. Fo example if file parameter is not specified Syncano will search for src/<filename>.js... with path separator in it that can be troublesome.

[23doors]

Haven't tested it but checked the code and seems that it should look for src/charge/createCharges.js in this case and work correctly with path separators

[mkucharz]

@23doors do you think we should support it? It is a nice twist, but it is not gonna work with windows (not sure if we will ever try to bring support in non-linux env).

[23doors]

@mkucharz hm. It should work on windows as well. Unless I misunderstood something. Backend should deal with it normally (as we're dealing with a zipfile anyway so path delimeter is always the same for us) and node also seem to always use '/' in require as path delimeter (at least I wasn't able to find any info about it being different). So it seems there is no harm in adding support for it in s call as well.

[mkucharz]

@23doors @Andela-callen ok, I'll try to support that feature then