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
By introducing a standard and providing a built-in way to bundle public-api files in a library LLM's will be able to understand the public API by querying the files from the local nuget cache.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
When using LLM coding agents then often make mistakes when using libraries since they don't know what's the API of the latest version.
some recent agent skills to help with this - https://github.com/richlander/dotnet-inspect by @richlander & https://github.com/davidfowl/dotnet-skillz by @davidfowl
By introducing a standard and providing a built-in way to bundle public-api files in a library LLM's will be able to understand the public API by querying the files from the local nuget cache.
for example:
for the

azure.corelibrary we currently haveif we would have something like this:

using https://www.nuget.org/packages/Microsoft.CodeAnalysis.PublicApiAnalyzers
or using https://github.com/dotnet/sdk/tree/main/src/Compatibility/GenAPI and producing some like this

by having these files extracted LLM will be able to understand the public API really quickly without decompiling libraries
Beta Was this translation helpful? Give feedback.
All reactions