Documentation feedback: What is the Main Goal of Code Snippets in the Documentation? #10005
TaMaN2031A
started this conversation in
General
Replies: 1 comment 2 replies
-
|
Hey @TaMaN2031A great question! In the past our code snippets were meant to be illustrative but not necessarily fully working examples. For full working examples we usually directed users to our Cookbooks and Tutorials. That being said we are in the process of migrating and improving our docs. One of those items includes making our code snippets fully runnable and tested in our CI. Some early work on that can be seen here #9967 and here #9997. So yes in the future we plan on making these snippets full running examples. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
Are the code snippets in the documentation created to be run successfully, or are they just part of code that doesn't necessarily work, but only discuss the idea, aiming at not creating a large code snippet that could make the reader lose the main idea?
For example, the code snippet at the end of the AsyncPipeline documentation page. The code is not complete:
document_store,prompt_template, anddatavariables are not initialized, but are used. And there is also no component calledretriever. However, it's searched for in thepartial_outputs.Thanks!
Beta Was this translation helpful? Give feedback.
All reactions