Refactored tools to not utilize manifest.yaml #1226
Conversation
william-price01
requested review from
collindutter,
cjkindel and
dylanholmes
and removed request for
collindutter
|
Do we have an Issue or other information on why this change is being made and what its impact is? |
@collindutter requested I remove this from the framework. |
|
@cjkindel We've got an internal issue for this. |
| @@ -4,24 +4,11 @@ Building your own tools is easy with Griptape! | |||
|
|
|||
| To start, create a directory for your tool inside your project. All tool directories should have the following components: | |||
|
|
|||
| * `manifest.yml` with a YAML manifest. | |||
| * `tool.py` file with a tool Python class. | |||
| * `requirements.txt` file with tool Python dependencies. | |||
There was a problem hiding this comment.
@william-price01 while we're already in here, can you test if this is true? I think this is optional I could be wrong.
There was a problem hiding this comment.
Test if requirements.txt is required, if your tool must be called tool.py?
@collindutter
There was a problem hiding this comment.
Actually, both would be good to test.
Codecov ReportAll modified and coverable lines are covered by tests ✅ 📢 Thoughts on this report? Let us know! |
|
Let's hold off on this one as we might actually start using it for hosted tools. |
|
@vasinov and I talked offline. We're going to move forward with this change. Any hosted tool manifest will be a file unique to that cloud feature, not a part of the framework. |
collindutter
force-pushed
the
Refactor/Tool_creation
branch
from
c6e7b1d to
31de3ea
Compare
Describe your changes
Removed manifest.yaml requirements.
Issue ticket number and link
📚 Documentation preview 📚: https://griptape--1226.org.readthedocs.build//1226/