-
Notifications
You must be signed in to change notification settings - Fork 199
Incorrect *.deps.json selected leads to no functions found #172
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@fredriklrsn Thanks for the issue! Let me have a look. |
This may be causing #122 as well |
This is also causing the same issue when using "func start" from command line to run a function. This causes a /bin/output folder to be generated which contains multiple *.deps.json files, meaning the spec is empty |
I've confirmed that if I delete the other *.deps.json files in the /bin/output directory generated by "func start", the spec starts working |
Have you had time to investigate the issue yet, @justinyoo ? |
I basically followed the reproduction step defined at #188. However, I was only able to find one *.deps.json file under the Here's my local environment:
|
I also have the same issue that sample code swagger.ui does not work. Swagger.ui works only when the sample code is debug. But it doesn't work when |
I'm also having this issue in .NET 5. There is both a .deps.json for the project itself and the referenced library. But only if you start with My library project file looks like this:
|
@fredriklrsn It's resolved, and @vincentbitter 's contribution has been merged to the main repo (not yet published). Would you please try the new change on your end and let us know? |
Great. I will test as soon as it is published. |
hey @justinyoo , any updates on when this will be published? |
Probably a bit late since it is out of preview now, but I have tried testing this and been getting a different error so I have not been able to verify that it works. |
Uh oh!
There was an error while loading. Please reload this page.
I have an issue with the open api extension picking the wrong *.deps.json file when determining which dll to search for functions in. This leads to an empty documentation
It seems like the first *.deps.json file is selected.
and that it searches through the whole app directory and not just the "bin" folder for these files. The app directory may contain multiple *.deps.json, while the "bin" folder only seem to contain one (function.deps.json) which seems to be the one it should be looking for
Should it search for *.deps.json directly in the "bin" folder (variable: runtimepath) or search specifically for function.deps.json?
The text was updated successfully, but these errors were encountered: