microsoft
[Codespaces] No error message pops up when entering the uppercase of the existing function name
Environment: Remote Codespaces Build Version: 20210622.6
Repro Steps:
- Click "Create HTTP Function..." button -> Create a HTTP Function with name "
HttpTrigger1". - Click "Create HTTP Function..." button -> Create a HTTP Function with name "
HTTPTrigger1". - Check whether pop up an error message.
Expect:
Pop up an error message, like below:
Actual:
No error message pops up and create the function "HTTPTrigger1" successfully.
More Info: Vice versa, there is no uppercase/lowercase character validation when entering a function name on Remote codespaces.
Both the Portal and Codespaces (Linux) seem to be case-sensitive, but when you actually hit the HTTP triggers...
It's not case-sensitive at all. I think this might actually be a bug on the platform as well.
@anthonychu
I think this is a functions issue when developing on a case sensitive FS and deploying to a case sensitive FS. Probably an edge case we haven't tested for before. What's likely happening is that the functions host is loading the 2 as separate functions, but behind the scenes it's using ASP.NET and its routing is case-insensitive by default, so one route is hiding the other at runtime.
Not sure the best place to fix this, perhaps we should fix them in tooling:
- vscode-azurefunctions should not allow the creation of the function of the same name but different case
- check that func behaves properly. My guess is that it would need to be fixed as well.
We could look into updating the Functions host to use case sensitive routing or fail at startup when this is detected, but both are breaking changes.
My suggestion is to repro this with just Functions on Linux and filing issues in the appropriate tooling repos.
Can't produce on WSL anymore, but can on Codespaces. ~~I think using the AzExtFsExtra in Functions can resolve this~~ It does not.
This issue has become stale and is at risk of being closed. The community has 60 days to upvote the issue. If it receives 5 upvotes we will keep it open and take another look. If not, we will close it. To learn more about how we handle issues, please see our documentation.
Happy Coding!
