-
Notifications
You must be signed in to change notification settings - Fork 722
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: add Foxy Contexts to additional resources #352
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Is this specific to foxyapps.com? If so, can you please explain it as such?
No, it has no relation to that website except for accidental collision in first word. I have named my library foxy after "fx" framework that is used for dependency injection and "contexts" after MCP's middle name. |
@strowk Hmm, I'm a bit confused by this mention in the README, then:
What is a "FoxyApp" here? |
It is just a builder that wraps "fx" app, which is why it has "App" word. No relation to website you linked. Coincidences happen as there are only so much words in english :) See here in godoc: https://pkg.go.dev/github.com/strowk/[email protected]/pkg/app#FoxyApp
I could probably rename this particular structure to AppBuilder or simply Builder so users can refer to it as UPD: I have renamed that structure to be simply Builder and it is referred to from other packages as app.Builder to avoid any extra confusion, plus it describes the nature of that structure better. |
Description
This adds a library to list of additional resources in README.
Motivation and Context
Library helps Golang developers to quickly bootstrap new servers.
How Has This Been Tested?
I took functional testing approach: https://foxy-contexts.str4.io/testing
Types of changes
Checklist
Additional context
The lib embraces DI concept to allow for more scalable development. It also very nicely works with generating new tools with LLM, as they just need to get an example of a tool with whatever context is injected to understand how to build a tool with same dependencies, but different logic. Compared to approaches where API has a
setRequestHandler
handler method and LLM have to be explained how to modify a file with all the other tools, here LLM only needs to focus on one tool at a time.