started setting up tests for client queries
Query API should take in a set of key value pairs instead of a map
Omg, I just realised how to effectively use protocols - this changes EVERYTHING
Sorted out the query stuff so it works via applying a sequence of key value pairs rather than passing a map all over the bleeding show
failing tests, but we have a protocol defining a surface area for our document database - woop
Still won't build - but yeah, let's not try and be clever about remote/embedded - make it a manual decision
Tests are passing against the new protocol for what a database should look like
Work to make the query API consistent so the documentation makes sense