Manuel
Manuel
BREAKING CHANGE: Route pattern syntax across cloud routes and rate-limiting now use the new path-to-regexp v8 syntax; see the [migration guide](https://github.com/parse-community/parse-server/blob/alpha/9.0.0.md) for more details.
@Moumouls Do you want to review this before we merge?
Point (1) is outside of our scope. It's a 3rd party repository and anyone is free to use it or contribute to it. We just need to be mindful that...
We can do that. What are the classes / namespaces where you see the most incompatibility to `@types/parse`? Are there just a few or is this an issue across the...
Could you please take a look at the failing CI jobs?
I haven't validated the issue yet. It may be a false positive. There should be tests for the token expiration we should look for.
It would be interesting to find an adapter-like concept to add such APIs. We currently have a GraphQL implementation which was implemented as a fixed part of parse server, but...
> If I'm understanding correctly, you're suggesting first writing a generic interface based on parse server's current feature set Maybe that generic interface does already exist - we could use...
@MajorLift Nice, I'll add a bounty to this, as I think it would be quite a great extension to make Parse Server more versatile and interoperable. And it could lighten...
What would a rough roadmap look like for this issue and where would the swagger file fit into it?