Repository navigation
Support for Config #34
Description
One of my favorite features of Parse is Config. Well, we definitely can create a custom method, that returns a JSON and etc., but would be amazing to have it working without the need to change code in the Client side.
What are the reasons that cause Config not to be supported currently? Maybe answering this question will give some direction on how to implement it?
Activity
flessard commentedon Jan 29, 2016
+1
kingmatusevich commentedon Jan 29, 2016
+1
AdityaShirole commentedon Jan 29, 2016
+1
gfosco commentedon Jan 29, 2016
The two of us building this didn't put a high value on Config, but we totally understand it is useful. I think adding support for it will be pretty simple. I'd venture that this would be a good first PR for someone learning the project.
natanrolnik commentedon Jan 30, 2016
Hey @gfosco, great idea!
I took a look on the SDK to understand what is the endpoint -
PFRESTConfigCommandgenerates a GETconfig. Also, noticed that it saves the last config in the MongoDB.What would be, in your opinion, the correct approach to this?
First, how would we add new parameters or edit existing parameters? Only via REST API, or through some UI similar to what we have today?
Secondly, how do you suggest creating the class that will handle the GET request?
gfosco commentedon Feb 2, 2016
Parse Config only hosts a single endpoint for clients, a GET on /config
Check
analytics.jsandinstallations.jsfor example route handling.Sadly, we named something
config.js.... So, we either have to renameconfig.jswhich would not be fun, or perhaps handle the /config route inindex.js.Then, we need a way to actually set the config values... Perhaps a POST against /config with the master key. And we should cache the values...
theill commentedon Feb 7, 2016
Gave it a first shot with #283
gfosco commentedon Feb 14, 2016
Merged in #283. 👍
Merge pull request #34 from back4app/fix_User_import