Api params #29
Api params #29
Conversation
|
|
||
| Dynamic routes (e.g. `/api/users/:id`) can be specified by using brackets in file or directory names as follows: | ||
|
|
||
| - Required parameter: Single brackets `<root>/functions/api/users/[id].js`. |
There was a problem hiding this comment.
Interesting one! I actually came to raise a ticket right now 🙈 something similar. But then I saw one open PR, so thought let me look at what you been cooking 😝
I am seeing an issue with the dynamic route workaround I had implemented (If you dont remember, just in case #L4).
Nested routes not able to fetch defineEdgeProps. I have defined the a folder same as the route in the functions for props.
So would this fix this issue too?
There was a problem hiding this comment.
@tbgse No, this is only for the api folder. The props don't have URL parameters since they rely just on the route name.
Nested routes not able to fetch defineEdgeProps
Can you try to assign a simple name to those routes? Likename: 'projects', and then create afunctions/props/projects.jsfile?
Also, try to check dist/functions.js and see if the exported object has the correct names and paths.
Closes #28