-
Notifications
You must be signed in to change notification settings - Fork 219
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
Error when generating an API plugin #4715
Comments
Looks like the extension shows/sends Authored #4722 to resolve the issue with the indexer cleanup logic that doesn't add a wildcard for the last indexer. |
@andrueastman will this fix the extension showing the wrong path? FYI @ElinorW |
The extension will show the deduplicated paths This is similar to the scenario to the test at
|
What are you generating using Kiota, clients or plugins?
Kiota plugin
In what context or format are you using Kiota?
Windows executable
Client library/SDK language
None
Describe the bug
I'm able to search and find the GitHub OpenAPI description and select the endpoints I care about, which are:
When trying to generate an "API Plugin" for the above endpoints, I got the following error:
In the output folder, both generated files (plugin and sliced openapi) are wrong.
Plugin file has no functions nor runtimes objects.
The sliced OpenAPI description has no "paths".
Using the same extension version I'm able to correctly generate an API Plugin for other GitHub endpoints, like
/search
node.Also, after getting the above error, I'm not able to load a new OpenAPI description. For that, I need to close and reopen VS Code.
Expected behavior
I should be able to generate an API plugin with functions and runtime for the selected endpoints as well as have a sliced OpenAPI description with only the selected endpoints in the paths
How to reproduce
Just try to generate a plugin for all the following endpoints:
Open API description file
No response
Kiota Version
plugin feature
Latest Kiota version known to work for scenario above?(Not required)
No response
Known Workarounds
No response
Configuration
No response
Debug output
Click to expand log
```The text was updated successfully, but these errors were encountered: