Open takanabe opened 3 years ago
Any fix for this?
The team is aware of the request. We do not have an update to share at this time. However, we do tag PRs with issues they solve. Once the team prioritizes and solves it, you will be able to see that link in the issue
Once more vote +1 from me to solve this one.
I vote +1 to solve this one.
hey, any updates on it?
Describe your idea/feature/enhancement
I encountered the following error when I executed
sam local start-api
This is because I use
/users/{something-name}/resources
as an API GW path parameter and Flask/werkzeung cannot accept path parameter names including-
.I could not notice that I cannot use path parameters except for
/[a-zA-Z_][a-zA-Z0-9_]*/
until I read the code and documents of Flask and werkzeug. So, I want to clarify these implicit conventions forsam local start-api
.Proposal
Fistly, I want to know if the behavior above is a bug or an intentional design for the
sam local start-api
command.Then I want to know how we can make the implicit rule clear. There are several options I can think of:
-
to_
in during path convensions although it's tricky for users.Additional Details
I plan to push PR based on the feedback from the maintainer of this repo but want to know which is the right direction for this project.