You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ ] Regression
[x] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.
Current behavior
We are currently using the same source for a local deployment (main.ts) and also an Azure deployment (main.azure.ts)
Swagger is working as expected with the installed node version (node dist/src/main.js) but is not working using the installed Azure Functions Core Tools (func host start --useHttps --cors * --verbose).
If is started using local azure functions files are not loaded as seen in the following image.
Expected behavior
Should show the UI without problems as seen below:
Minimal reproduction of the problem with instructions
I'm submitting a...
Current behavior
We are currently using the same source for a local deployment (main.ts) and also an Azure deployment (main.azure.ts)
Swagger is working as expected with the installed node version (node dist/src/main.js) but is not working using the installed Azure Functions Core Tools (func host start --useHttps --cors * --verbose).
If is started using local azure functions files are not loaded as seen in the following image.
Expected behavior
Should show the UI without problems as seen below:
Minimal reproduction of the problem with instructions
main.azure.ts (not working)
main.ts (working)
What is the motivation / use case for changing the behavior?
Environment
Would be nice if somebody can help us with this issue. I guess its a weird configuration issue.
Thank you anyway and bye
The text was updated successfully, but these errors were encountered: