Payloadcms v3 custom endpoint wildcard bug

Question

Hey I am migrating to v3 rn. Im having issues with the custom endpoints.

previously i could use path: '/find-by-path/*'. So i had a wildcard in the end of my path that i could use to capture the rest of the slugs via the route.params.

This doesnt work in v3.

No matter what im trying to do I get a Unexpected MODIFIER at 5, expected END With 5 being the pos of the '*' in the path.

I sadly couldnt find any information out there. Official docs never mention wildcards.

Any help apprecieted

Best Regards, Jan

Drake · Accepted Answer · 2025-02-10 22:30:01Z

0

I got an answer on the github issue I made for this.

/path/(.*) does the same as /path/* did.

answered Feb 10 at 22:30

Drake

72 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Payloadcms v3 custom endpoint wildcard bug

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related