Export non-echo schemas

[cpfiffer]

Mostly a convenience PR to permit direct schema access. I typically use Ollama exclusively, so it's nice to be able to do

aigenerate(OllamaSchema(), ...)

instead of

aigenerate(PromptingTools.OllamaSchema(), ...)

[svilupp]

Is it okay if I run a quick poll on Slack first?

I was trying to be conservative with exports, since some users have it in their startup.jl
Btw since users only ever need 1 our of the 10ish schemas and that list will grow a lot
over time, isn’t it a bad precedent?

2 workflow questions

• why not import OllamaSchema specifically when you import PT?
• why not just register the model (PT.register_model!) you use at the top of the script? Then you never have to provide schema. In my usage, I never use the schemas because the models set them for me.

[svilupp]

The specific workaround I mentioned was: https://siml.earth/PromptingTools.jl/dev/examples/working_with_ollama/#Schema-Changes-/-Custom-models

PT.register_model!(;
    name = "llama123",
    schema = PT.OllamaSchema(),
    description = "Some model")
PT.MODEL_ALIASES["l123"] = "llama123" # set an alias you like for it

Then you can simply run: ai"Say hi"llama123 (no need for any schemas)

[cpfiffer]

I'm typically against const PT = PromptingTools, usually I prefer to export relatively judiciously (especially since these names are extremely unique and unlikely to clash).

Users who prefer to prefix by package name should probably use import, or at least that's been my take. using is for quick-and-dirty access, and if you use it you are typically doing so for access to exports from the package.