Skip to content

Documentation (at least Google-related) is an outdated mess. #2289

@vykintazo

Description

@vykintazo

Is it known that the docs are badly out of date and very confusing or outright not true?
At least Google provider related ones, here are some examples:

1. 3 separate providers listed in Integrations

  • Gemini
  • Google GenAI
  • Vertex AI (deprecated)

Relation between Gemini vs GenAI is especially unclear as the seem to be one of the same, but docs slightly differ.

2. Outdated "limitations" of Google provider

  • Optional values appear to be working, Enums also work in GENAI_STRUCTURED_OUTPUTS mode.

3. Incorrect/inconsistent Vertex AI migration info

Docs say google/<model> + vertexai=True is deprecated and vertexai/<model> should be used, but code would emit deprecation warnings which say exactly the opposite:

elif provider == "vertexai":
warnings.warn(
"The 'vertexai' provider is deprecated. Use 'google' provider with vertexai=True instead. "
"Example: instructor.from_provider('google/gemini-pro', vertexai=True)",
DeprecationWarning,
stacklevel=2,
)

4. Incorrect mode enums.

Docs mostly specify Mode.TOOLS, Mode.JSON like here or here or here and I think basically everywhere. Yet code would throw an error on those as only GENAI_TOOLS and GENAI_STRUCTURED_OUTPUTS are supported:

valid_modes = {
instructor.Mode.GENAI_TOOLS,
instructor.Mode.GENAI_STRUCTURED_OUTPUTS,
}

I found this issues quite weird given that otherwise this library seems to be well maintained.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationtype:docs-outdatedDocumentation is outdated or needs updating

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions