{"push_id":938586905,"size":1,"distinct_size":1,"ref":"refs/heads/feature/recommend","head":"72d76d427f05b840c18f9cba8aa7ba56a710a881","before":"97b5cff942f5e235f7fdbc45f5189640001cf704","commits":[{"sha":"72d76d427f05b840c18f9cba8aa7ba56a710a881","author":{"email":"6bba1fa7b2078c5737b9d3bfef4e9449fc4915d1@printed.com","name":"Alex Moon"},"message":"Recommendation - we have a working system - this was a massive pain in the ass:\n\n1. String concatenation of a '.*' to the {0} param is not intuitive - we've learnt our lesson, however\n2. By god - why in FUCK is the method resolver not enabled in Spring Handlebars by default?\n3. Beans can't have the same name - we need to think of a way to differentiate neo4j services and SQL services - though\n   btw even better would be NOT to differentiate between these - a service should be able to pull from multiple data\n   access modules - and indeed, should probably be responsible for composing these the same way Controllers are responsible\n   for composing Services\n4. Not entirely convinced Neo4J interface should actually use entities really... we need to get back tabular data from which\n   we can pull the SQL models...","distinct":true,"url":"https://api.github.com/repos/alex-moon/tree/commits/72d76d427f05b840c18f9cba8aa7ba56a710a881"}]}