Manuel
Manuel
@Moumouls What do you think?
Thanks, did you mean that you verified that the bug exists in PS8?
@coderabbitai > The transformation ensures compatibility with path-to-regexp v8 while maintaining backward compatibility for routes using named wildcards. This sounds like a workaround; what changes are needed in the codebase...
@coderabbitai, we'll release the new major version of Parse Server 9 shortly, so it would be a good opportunity to add breaking changes to the release. The option "1. Breaking...
@coratgerl instead of applying a patch we should fix the underlying issue, because otherwise we're just accumulating debt that eventually comes due in the future.
You can add a migration guide for PS9, following the style of the existing PS8 guide.
@coderabbitai what is this path-to-regexp v8 syntax? Is that a custom syntax or does it follow any wider known syntax? What is it similar to, regex, glob, etc?
@coderabbitai will express framework also adopt the new v8 syntax, or did it already adopt it?
Parse Server migrated to express 5 some months ago, in the migration guide we can simply refer to the [express migration guide](https://expressjs.com/en/guide/migrating-5.html#path-syntax) which is the same topic.
@coratgerl could you please fix the conflicts?