Skip to content

Why does the SDK convert things to camelCase? #76

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
KernelDeimos opened this issue Feb 7, 2025 · 1 comment
Open

Why does the SDK convert things to camelCase? #76

KernelDeimos opened this issue Feb 7, 2025 · 1 comment

Comments

@KernelDeimos
Copy link

I'm working on an integration of multiple AI services. Some are compatible with Claude's SDK, some with OpenAI's SDK, and some - like Mistral AI - have their own SDK.

For reasons I don't understand, this SDK coerces snake_case properties to camelCase. I suspect whoever made that decision thought "this will make the SDK look nicer" and didn't realize they were breaking compatibility with code written against conventional SDKs.

My two questions are:

  • why?
  • can we fix it?

My suggestions are:

  • release a major version where the camelCase garbage is scrapped
  • add a parameter to make the SDK follow conventions

Someone could make the argument "this is a different SDK, and it can have its own conventions". My counterargument here is that it literally does follow the standard conventions if we just simply get rid of this camelCase thing; code written to work with OpenAI's SDK will suddenly work with Mistral's SDK without any changes.

@KernelDeimos KernelDeimos changed the title Why does the SDK convert things to snakeCase? Why does the SDK convert things to camelCase? Feb 7, 2025
@KernelDeimos
Copy link
Author

Well... at least this isn't nearly as unique as Gemini's SDK

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

No branches or pull requests

1 participant