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
The very best thing we could do for usability is to get the *.api comments captured into the json files so we could then convert them to comments on the generated APIs. The usability, particularly to users who aren't in vpp code day in and day out would be huge.
The very best thing we could do for usability is to get the *.api comments captured into the json files so we could then convert them to comments on the generated APIs. The usability, particularly to users who aren't in vpp code day in and day out would be huge.
However, that is not really what this issue is about. This issue is about creating user guide document for using GoVPP - how to call VPP API and use Stats API in general. The specific API messages and their usage/comments are out of scope and can rather be tracked in another issue.
I rebased gerrit change: vppapigen: include comments in json and pinged Ole about the status. He is fine with the patch but it has not been tested. @ondrej-fabry , can you please open a new issue & test that this patch works with GoVPP?
This issue tracks progress of creating User Guide document for using GoVPP.
Here are few ideas for topics to cover:
Channel
vsStream
StatsAPI
vsStatsProvider
(posted by @VladoLavor in Create Troubleshooting Guide document #60)The text was updated successfully, but these errors were encountered: