Add optional caliban endpoint

[vpavkin]

Fix #5

For some reason I bumped into foundweekends/giter8#432, although giter plugin version is up to date.

The only consequence so far is that there's an unneeded html file in resources folder if user opts out of caliban endpoint

[marioosh]

Does it work?? Actually I'm missing one part (maybe it's automagically covered by caliban somehow - I don't know, don't know the library so far.... :D
JSON sent to the endpoint is like this:

 { operationName: "", query: {}, variables: {} } 

query is compared along schema and passed to the executor. I don't where it's parsed, so the reason of my question. Are you able to run server and make a query in graphiql console?

[vpavkin]

@marioosh WRT how the endpoint works - I'm pretty sure it is, because I tested it with Altair. It even gets the docs properly, so you don't have to type queries by hand.

[vpavkin]

So this is hanging for long time already :) Should I merge it after #33 is merged?

[jczuchnowski]

@vpavkin @marioosh sorry I've been delaying it for so long. Looks great. One thing I've been thinking is that in case someone opts out of the GraphQL endpoint, still gets the additional repository and service methods for deletion events, custom search by price etc. Don't you think it would be better if these would also depend on $if(add_caliban_endpoint.truthy)$ ?

[vpavkin]

@jczuchnowski great catch, I missed that entirely. I can clean it up on monday

[jczuchnowski]

Don't you have holidays on Monday? :)

[vpavkin]

Nope, my holidays start on 1st of May:) Actually finished project a day earlier, so plan to merge this today :)

[vpavkin]

@jczuchnowski I added a small cool thing to CI - it now runs tests for both caliban and non-caliban versions of the template. will be handy since we have a lot of conditionals there and it's easy to miss something.

[vpavkin]

Cleaned everything, at least it seems so :)