Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Consider go type name when autobinding #2812

Merged
merged 1 commit into from
Sep 28, 2023
Merged

Consider go type name when autobinding #2812

merged 1 commit into from
Sep 28, 2023

Commits on Sep 28, 2023

  1. Consider go type name when autobinding 

    Currently, generated schema type names are normalized, for instance - SomeTYPE in the schema will be generated as SomeType in the model.

When autobinding, however, we only consider the schema type name when searching for it in the relevant package(s),
thus type names that differ post normalizations aren't auto-bound properly and are instead re-generated.

This commit suggests a fix where we'd try to autobind for both the schema type name (first, to maintain back compat), or the go type name if the former isn't found.
    @dany74q
    dany74q committed Sep 28, 2023
    Configuration menu
    Copy the full SHA
    33ff2fa View commit details
    Browse the repository at this point in the history