Features Endpoint for Dashboard.

[peterdotjs]

Features endpoint based on discussion #611

[drew-gross]

Sweet! I think @nlutsenko made a middleware for enforcing master key on an endpoint, but otherwise LGTM.

[nlutsenko]

Yup, lgtm otherwise, encourage to use the middleware if you need to enforce the master key.

[peterdotjs]

@nlutsenko can you confirm you're referring to the middleware being used in FilesRouter? I'm not seeing it used in any of the PromiseRouter files.

[facebook-github-bot]

@peterdotjs updated the pull request.

[nlutsenko]

@peterdotjs Yes, there was functionality added by @flovilmart that allowed plugging middleware into PromiseRouter.

[drew-gross]

I think we can probably skip the single element array. Also, I remembered the that endpoint for getting a single schema doesn't use results :( so maybe it's not critical

[flovilmart]

@peterdotjs the problem with the middleware thing is that it doesn't exit early... for some obscure reason returning a Promise.reject() keeps it going

[drew-gross]

Oh yeah, were you going to include the server version in this endpoint? I wanted to display it in the apps index. Also it would be pretty sweet to have the server "version" be a git hash or something if you are hacking on the server.

Fake edit: The output of git describe --dirty sounds ideal for the "version" while you are developing.

[drew-gross]

Sorry for all the scope creep :( feel free to ignore

[drew-gross]

Note: Logs endpoint is different from the Parse.com logs endpoint, so it should be marked as not supported until we can get feature parity (enough for the dashboard to work, at least

[flovilmart]

@drew-gross could we get a spec for the logs endpoint?

[drew-gross]

Easiest way is probably to go to dashboard.parse.com and view the two logs pages and capture the request.

[drew-gross]

Config endpoint also doesn't match close enough to use on the dashboard.

[flovilmart]

I can work on that

[drew-gross]

Merging this myself so I can do some work on top of it.