Add all the new component docs to the site and do a tidy up of docs (#7098)

* feat: add all the new component docs to the site

* fix(docs): relative links and markdown warnings

* feat(docs): How to contribute to the docs as a docs section

* fix(docs): missed docs page for developer setup

* fix(docs): re-add configurations options

* fix(docs): bad link to components fixed

* fix(docs): bad link to components fixed

* ref(docs): reorder some items to make more sense

* fix(docs): bad indentation and duplicate block

* fix(docs): warning about out of date markdown extension

* fix(docs): broken links fixed

* fix(docs): markdown formatter complaints
This commit is contained in:
Nicholas Tindle
2024-04-23 08:49:07 -05:00
committed by GitHub
parent fd3f8fa5fc
commit 5e89b8c6d1
18 changed files with 159 additions and 92 deletions

View File

@@ -0,0 +1,11 @@
# Advanced Components
## General
Debugging may be easier because we can inspect the exact components that were called and where the pipeline failed (current WIP pipeline):
![Modular Pipeline](../../imgs/modular-pipeline.png)
Also that makes it possible to call component/pipeline/function again when failed and recover.
If it's necessary to get a component in a random place, agent provides generic, type safe `get_component(type[T]) -> T | None`