Skip to content

feat: console @ai-sdk generation warnings #186

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

yusuf-eren
Copy link

@yusuf-eren yusuf-eren commented Jul 8, 2025

example warning log with @ai-sdk/[email protected]

@ai-sdk generation {
  type: 'unsupported-setting',
  message: 'Unknown warning',
  details: 'JSON response format is not supported.',
  model: {
    modelId: 'claude-3-7-sonnet-20250219',
    version: 'v1',
    provider: 'anthropic.messages',
    supportsStructuredOutputs: undefined
  }
}

Copy link

changeset-bot bot commented Jul 8, 2025

⚠️ No Changeset found

Latest commit: 542ff5b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@yusuf-eren
Copy link
Author

Hey @seratch , should I add changesets to this PR?

@seratch
Copy link
Member

seratch commented Jul 10, 2025

I haven't made sure if this change is really useful but yes, a changeset file is necessary if it gets merged.

@dkundel-openai
Copy link
Collaborator

@yusuf-eren does the AI SDK log those warnings out by default? If not I would say let's keep the same behavior they have and not log them out automatically. At least not on a warn level. I'd be okay with having them at a debug level. Otherwise they should be available under modelResponse.providerData.warnings for people to handle them themselves. An entry in the docs could be helpful for that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants