Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Cloud function doesn't return Parse.Object #93

Closed
Tux1 opened this issue Jan 31, 2016 · 2 comments
Closed

Cloud function doesn't return Parse.Object #93

Tux1 opened this issue Jan 31, 2016 · 2 comments
Labels
type:bug Impaired feature or lacking behavior that is likely assumed

Comments

@Tux1
Copy link

Tux1 commented Jan 31, 2016

Hi,
I am moving to my own Parse Server thanks to your guide and your release.

I just have question on Cloud Function.
I have got some functions returning Parse.Object. When I use the Parse backend, I get Parse.Object (extended or not). When I use my own server, Cloud function returns regular JS object instead of Parse.Object.
Is it the correct behavior or that's a bug ?

Thanks !
@gfosco gfosco added the type:bug Impaired feature or lacking behavior that is likely assumed label Feb 2, 2016
@gfosco gfosco mentioned this issue Feb 3, 2016
Closed
@natanrolnik
Copy link
Contributor

Should be pretty simple to solve I imagine.
@gfosco is there any PR already taking care of this? If not, could you give us some direction? Is this related to here?

montymxb pushed a commit to montymxb/parse-server that referenced this issue Feb 14, 2016
@gfosco
Merge pull request parse-community#93 from ParsePlatform/gFosco.count…
ad2aab6 
…-sessiontoken

Added sessionToken to the count() query.
@gfosco
Copy link
Contributor

gfosco commented Feb 20, 2016

Please re-open if you're still experiencing this issue on 2.1.2.

@gfosco gfosco closed this as completed Feb 20, 2016
@Tux1 Tux1 mentioned this issue Feb 21, 2016
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type:bug Impaired feature or lacking behavior that is likely assumed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@gfosco @natanrolnik @Tux1