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
I have been formatting the X-Pack API reference information such that it uses the same section headers as the Cloud Enterprise documentation, which in turn was generated from Swagger.
I would like to pursue whether we can go one step further and start generating the X-Pack API information from Swagger too. This would help avoid situations where the documentation gets out of synch with the API code.
If it is not possible to include our current level of code snippet testing in the Swagger-generated files, we will need to investigate options for appending that information.
The text was updated successfully, but these errors were encountered:
Original comment by @lcawl:
This issue is related to #25152
I have been formatting the X-Pack API reference information such that it uses the same section headers as the Cloud Enterprise documentation, which in turn was generated from Swagger.
I would like to pursue whether we can go one step further and start generating the X-Pack API information from Swagger too. This would help avoid situations where the documentation gets out of synch with the API code.
If it is not possible to include our current level of code snippet testing in the Swagger-generated files, we will need to investigate options for appending that information.
The text was updated successfully, but these errors were encountered: