Manuel
Manuel
@coratgerl let's just consider the insights already gained in existing PRs. What't the diff between your PR and https://github.com/parse-community/parse-server/pull/9651?
@RaghavArora14 Sure, I see you have asked also on other issues. In general you don't have to ask. If there is no active pull request for an issue then it's...
@RaghavArora14 This is still up for grabs, if you are interested.
@AshishBarvaliya maybe interesting for you
@syedbarimanjan regarding the side panel, maybe take a look at https://github.com/parse-community/parse-dashboard/pull/2584#issuecomment-2284491339; it also adds a side panel. We'd want to use a lightweight lib for the graph rendering, with an...
@syedbarimanjan The PR has been merged.
HI @weinStag, thanks for the PR, I've updated your PR description to link it to this issue.
This can be merged for PS9, with the note in the changelog that it also disables `Parse.Query.includeAll` by default. See also https://github.com/parse-community/parse-server/issues/9939#issuecomment-3566667002.
@coderabbitai suggest good practical default values for `maxGraphQLQueryComplexity` and `maxIncludeQueryComplexity`.
@parse-community/server Any breaking changes that you'd like to see getting merged into Parse Server 9, please post them here.