Parse.com plugin v2

Solar2D General Questions/Discussion
#121

I’ve looked as well and could not find the source there. Please advise.

#122

Hi folks,

First, my apologies for the unclarity. I think one issue is that I worked on a lot of these projects before I was hired on at Corona. As such, I now have assigned tasks that I must prioritize. Previously I could work on whatever, whenever, but that is no longer the case.

In regards to the Parse plugin, Corona itself has no responsibility to update it or even host it. It is/was a personal project.

With that in mind, I have opened up the repo publicly (I totally forgot to set it public when I talked with Rob).

Please note that this is a Corona “plugin” and not just a drop-in module. As such you should be familiar with how plugins are structured, and built: https://docs.coronalabs.com/native/plugin/index.html#lua-only

If anyone wants to maintain the project, I’ll be more than happy to add serious contributors. The actual distributed plugin can only be compiled from the main repo.

And without further ado (whatever that means): https://bitbucket.org/develephant/corona-plugin-parse

Additionally, if you feel this is an important plugin, then please make sure the upper staff know that. I don’t make those decisions.

Again, sorry for the miscommunication. It’s possibly sleep related (or lack of).   :wink:

Cheers.

#123

Hi Chris,

Thanks for making the repo public. We’ve been using a temporary wrapper we’ve made, but now we can start reverting back to your plugin and start fixing the issues we’ve been facing.

Expect a pull request in the near future.

Cheers,
Shehab

#124

Hi Shehab,

I got your recent fix, thank you very much! I’m sure you’ve made the community happy as well. :slight_smile:

The latest “plugin” should compile and deploy over the next few hours or so.

Cheers.

#125

Hi @Rob,

Small question, is it possible that plugins get built with old code? Currently when I clone the parse plugin repo and test locally, everything works like a charm. But when I let the simulator download it, it still crashes on the same old error.

What do you think could be causing this?

#126

The plugin would have to be updated on our server before the simulator could download it. I don’t know if this plugin has been updated on our servers recently or not.

#127

Recently I deployed Parse-Server to Heroku and redirected my Corona client application to use that using the Parse plugin.

 

The queries work fine with no params. But once I add params they fail. A little debugging from Heroku logs show, that the path formed using the Parse plugin is different than when using curl or the mod_parse module:

 

with-plugin: 

path="/parse/classes/Category?order%3dname"

without-plugin (curl or mod_parse): 

path="/parse/classes/Category?order=name"

 

Using the plugin I get the error: 

{"error":"Invalid paramater for query: order=name","code":102}

 

Below is an example using the plugin:

 

local parse = require('plugin.parse') parse.config:cloudAddress("http://myappname.herokuapp.com/parse") parse.config:applicationId("myAppId") parse.request(parse.Object.query, "Category") :where({["is\_empty"] = false}) :options({ ["order"] = "name" }) :response(callback)
#128

I too am trying to migrate from Parse to a self hosted solution. However, it seems that parse plugin behaves differently when connected to the self hosted solution. For example, the code that should have created a new user on the DB now simply returns the list of existing users. Please advise.

#129

Hi develephant,

I understand you’re working on other projects now, but we rely on parse plug-in for past and hopefully future projects. If you can’t maintain the plug-in can you release its source to the community so we can continue its development? It was bad enough that FB decided to cut Parse off leaving us scrambling for alternatives and delaying our schedule by weeks. Just when we thought that we are past that obstacle, device testing shows additional quirks that were not there before.

Today I encountered yet another issue where the behavior is different between the cloud and Parse.com and I would have loved to debug the plug-in or simply review its code to identify the source of the problem.

#130

Been blocked on this since the 9th of June, a little over a month now. Any word from the Corona staff on whether this will be addressed or dropped?

#131

Regarding query with params, I’ve found out that using the original :options( params ) is not working. instead use :data( params )

#132

I talked with @develephant and he said that the plugin is now open source and he’s not in a position to continue to support it. He made that announcement a while back. The Parse plugin was never a Corona Labs maintained product. We offer it through the store as a third-party created solution. If someone is interested in taking it over, it is open source. You could fix whatever and resubmit it and take ownership of supporting the plugin.

Rob

#133

Thanks for the clarification @Rob, can you kindly link me to the open source Parse Plugin repo?

#134

I’m not for sure, but here’s @develephant’s github: https://github.com/develephant?tab=repositories

#135

I’ve looked both @develephant’s github and bitbucket, but I couldn’t find the repo for the Parse Plugin. Only a repo for the documentation of the Parse Plugin.

That’s why I’ve been a bit frustrated lately. If it’s open source, I’m completely fine with fixing issues and maintaining the plugin. If it’s not, and there won’t be any more updates, I’d like to know so that I can remove the plugin completely from my projects and move on. 

#136

I’ve looked as well and could not find the source there. Please advise.

#137

Hi folks,

First, my apologies for the unclarity. I think one issue is that I worked on a lot of these projects before I was hired on at Corona. As such, I now have assigned tasks that I must prioritize. Previously I could work on whatever, whenever, but that is no longer the case.

In regards to the Parse plugin, Corona itself has no responsibility to update it or even host it. It is/was a personal project.

With that in mind, I have opened up the repo publicly (I totally forgot to set it public when I talked with Rob).

Please note that this is a Corona “plugin” and not just a drop-in module. As such you should be familiar with how plugins are structured, and built: https://docs.coronalabs.com/native/plugin/index.html#lua-only

If anyone wants to maintain the project, I’ll be more than happy to add serious contributors. The actual distributed plugin can only be compiled from the main repo.

And without further ado (whatever that means): https://bitbucket.org/develephant/corona-plugin-parse

Additionally, if you feel this is an important plugin, then please make sure the upper staff know that. I don’t make those decisions.

Again, sorry for the miscommunication. It’s possibly sleep related (or lack of).   :wink:

Cheers.

#138

Hi Chris,

Thanks for making the repo public. We’ve been using a temporary wrapper we’ve made, but now we can start reverting back to your plugin and start fixing the issues we’ve been facing.

Expect a pull request in the near future.

Cheers,
Shehab

#139

Hi Shehab,

I got your recent fix, thank you very much! I’m sure you’ve made the community happy as well. :slight_smile:

The latest “plugin” should compile and deploy over the next few hours or so.

Cheers.

#140

Hi @Rob,

Small question, is it possible that plugins get built with old code? Currently when I clone the parse plugin repo and test locally, everything works like a charm. But when I let the simulator download it, it still crashes on the same old error.

What do you think could be causing this?