tdobson
commented
3 weeks ago There's not a sort of regular way of doing that easily within standard operations. I have sympathy for this, as I personally use a framework called Mantine and it's fairly new and rapidly changing (and I love it), but it means the models are frequently wrong unless I supply the docs.
There's no super standard way (at present) of saying "yo aider, the docs are here" other than perhaps scraping them all into a file and including them in the repo(?) or one off searching for the docs needed and adding them with /web or copy/pasting the relevant docs into the request you send aider.
I have a sense that as caching requests in some models becomes cheaper and more prevelant, we'll provide the docs to the models alongside the code, eg /add frameworkManual.md
paul-gauthier
djl0
Issue
If I want to build something using a relatively new framework which may have changes in syntax or design patterns since the model was trained (eg LlamaIndex or Polars), is there a way to point to that repo locally where docs or the code live?
Version and model info
No response