-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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.
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
Check out this module for Parse.Cloud #4317
Comments
That’s a Neat little project you got here! I was thinking about discovery of such ‘addons’ / community packages, and that would be nice if published as: parse-server-addon-YOUR_PACKAGE_NAME what do you think? |
Very nice! Right now it is published as |
Now it is changed, and available in npm as |
Awesome! That will probably help discovery! I’ll check with others if we wanna move adapters to the same pattern parse-server-adapter-*. |
As promised, I did the Algolia addon I was talking about: It is available in npm as |
Pretty cool! I’ll make a PR on the README, so other users know about this new convention for community packages discovery. |
Can you please post these repos to parse-server-modules ? |
What do you mean by that? |
I see that in that account or repository you have linked several adapters for parse-server. Community made addons can appear there? |
Those are not linked. This organization was created when Parse-server was still under facebook’s management and for official adapters/reference implementations. Now, while your addons are quite useful in certain scenarios, I don’t believe they should live under this organization as it would form some kind of endorsement / official support. We have our hands pretty busy already, and i was actually thinking moving most of the official adapters back to parse-Community instead of parse-server-modules. |
Ohh I understand, I thought it was a list of repositories that would work
with parse-server, made by the community. Thank you!
2017-11-05 9:24 GMT-05:00 Florent Vilmart <notifications@github.com>:
… Those are not linked. This organization was created when Parse-server was
still under facebook’s management and for official adapters/reference
implementations. Now, while your addons are quite useful in certain
scenarios, I don’t believe they should live under this organization as it
would form some kind of endorsement / official support. We have our hands
pretty busy already, and i was actually thinking moving most of the
official adapters back to parse-Community instead of parse-server-modules.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#4317 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AG3gNUe3MdvsjU0Hf5jTsqdBg47Icbm5ks5szcUagaJpZM4QRxvm>
.
|
We can do a Awesome Parse Server list. |
Hello,
First I want to thank all the community for being so active, and the people who are working so we can have new versions of
parse-server
.I have been working with
parse-server
some time after Parse announced they were not going to continue, and I want to share with you a module I created for being able to manage more easily the Cloud Code. It is called ParseCloudClass and you can see it hereThe module
With
parse-cloud-class
module you can easily:The usage is very simple, like this:
A word on the addons
I think being able to use other community-made scripts for
parse-server
would be something very nice to have, and would continue to make our life easier as developers.In this way, using ParseCloudClass I think we could have in the future some modules to connect the data with some Analytics service like Mixpanel, or with other services such as Algolia; or even having a replication plugin that syncs the data with DynamoDB or any other database.
The only thing needed, would be that the new module implements
afterSave
orafterDelete
(there are more functions)Note
I am posting this here because I think somebody else would like to easily configure the Parse Cloud classes with this basic functionality, or extend it in the future.
The text was updated successfully, but these errors were encountered: