jimrhoskins/angular-parse

angular-parse's Issues

401 Unauthorized issue

Hi,

I got a 401 Unauthorized request response when I'm using your module. Maybe a malformed request ?

PS: I'm using your example.

Thank you

Bower support ?

Are you planning to implement it ?

The Parse.User has wrong path

As The User is extend from Model it gets its find method , in find method the path is hardcoded
thats why the User even with different @pathBase: -> "/users" has its path same as model /classes/
This obvious needs to be fixed

Remove dependency on CoffeeScript

I love what you have done but if I understand correctly what is said in your README, there is a dependency on CoffeeScript. I'm not really fan of the idea to learn and integrate CoffeeScript in the middle of AngularJS and Parse. Do you plan to implement the Javascript equivalent of what's possible with CoffeeScript anytime soon?

Problem with queries using comparison operators such as "$ne"

I have the following query:

Reservation.query(
  where:
    result:
       "$ne": "waiting"
).then (reservations) ->
....

which always returns 0 records. When I do the following and equivalent curl command, I get many returned:

curl -X GET \                                                                                                           
  -H "X-Parse-Application-Id: SOME_ID" \
  -H "X-Parse-REST-API-Key: SOME_KEY" \
  -G \
  --data-urlencode 'where={"result":{"$ne":"seated"}}' \
  https://api.parse.com/1/classes/Reservation

The following query doesn't use a comparison operator and works as advertised (but of course it's not the query I want since I have multiple values for result and want to filter out the 'waiting' values):

Reservation.query(
  where:
    result: "waiting"
).then (reservations) ->
....

Have anyone ever used a query with a comparison operator ($ne, $nin, $exists)? Is there something wrong with my query or syntax? Any help on this would be appreciated!

Thanks,
Bill

Missing ACL logic

ACL logic is not present, to do without ACL one needs to create a user column in tables to maintain relations, it is much harder to implements groups/roles and for every query to the Parse api i need to implement a filter.

I overcame this shortcoming by writing cloud code for Parse and setting the ACL on afterSave for object creation. If ACL logic can be implemented in Angular-Parse, I believe the tasks will be much easier then.

Initialize BaseURL issue

Parse.BaseUrl = 'http://someurl'
And it's get's a default BaseUrl: "https://api.parse.com/1", without ability to override it.
How can it be fixed?

Nested objects should be transformed to Pointers when model is saved

Fetch an object that has a pointer member by asking to include this nested object: MyModel.find(id, {include: 'child'});.

Then call save() on this object. Parse sends a Bad Request response: {"code":111,"error":"invalid type for key child, expected *Child, but got object"}

I think members with type __Object should be transformed to __Pointer when sent back to parse.
I will find time to work on this.