This is the same stack I've been using for a project at work, I was exited to see the Parse SDK wrapper but apparently it's a thin one. In my current project I have attempted to create a wrapper completely Parse-agnostic in hopes to be able to switch to another provider my changing a little config, it does the basics for now, but I'd have to rewrite it as it's a little tied to this specific project.
I'm curious to hear if anyone has done a similar effort or is serious about starting.
Do you have better docs on the Parse query calls. Im new to Parse and trying to figure out how to customize the query / collection inside of this. Trying like equalTo and those type of methods I just don't understand what part of the code to use. Do I write a custom service to pull it in or do I use ParseQueryAngular in a directive?
checkout Monster.js, there is an example there. Basically all your queries should be methods on the collections/models. Each data model is defined in their own file extending the ExternalDataServices service. No need to create a new service for every model.
This is the most common feedback we've had so we'll improve the docs in time.
20 comments
[ 2.7 ms ] story [ 50.5 ms ] threadI wanted to get into trying both things so coupling it makes me happy and more incline to get into both.
Thank you for sharing and congrats on making it into the Parse blog!
Amazing stuff.
I'm curious to hear if anyone has done a similar effort or is serious about starting.
But there is a big tradeoff for API user experience if you want to make it 'switchable' to another service.
Alternatively, for switching, there's this: https://github.com/stevegraham/parseport
This is the most common feedback we've had so we'll improve the docs in time.
Thanks!