Daniel
Daniel
Come to think of it do you really need `config.middleware` when using the Parse Server express constructor? Could you just use: ```js const app = express(); app.use(…custom middleware here) app.use("/parse",...
Thanks for the explanation! I think this could be solved by #7869 - exposing the config via `config.get`. I think using express’ native syntax of `app.use` for middleware is a...
Looks good so far @Moumouls! Would you see any value in adding a helper method to `Parse.Cloud` that can register auth, rather then it all being required in `index.js`? For...
I'm really looking forward to this!
I would assume the issue is happening somewhere around here https://github.com/parse-community/parse-server/blob/c1e808f9e807fc49508acbde0d8b3f2b901a1638/src/RestWrite.js#L1604
A workaround could be to use `enableExpressErrorHander` with: ```js app.use((err, req, res, next) => { let httpStatus; switch (err.code) { case Parse.Error.INTERNAL_SERVER_ERROR: httpStatus = 500; break; case Parse.Error.OBJECT_NOT_FOUND: httpStatus =...
Isn’t this a JS SDK issue/feature?
I'm happy to continue working through, just wanted to see your thoughts 😊
Still observed, dammit
I think so, I'm pretty sure the postgres tests are unrelated but not 100% sure