Skip to content

Returning $q instead of Parse.Promise causes issues with internal method calls #1

Description

@mcwebb

Sometimes Parse calls its own methods internally, wrapping all the methods in $q means that these internal calls sometimes error since they expect properties which aren't available on the $q object.
For example: _thenRunCallbacks(). For now I've disabled the Angularifying of some methods this affects, but that is obviously not a long term solution. Need to find a way to return an object which is more or less API compatible with $q and Parse.Promise. Perhaps move back to clone Parse instead of making ngParse a reference?

Metadata

Metadata

Assignees

Labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions