-
Notifications
You must be signed in to change notification settings - Fork 18
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
Handle potential naming collisions #20
Comments
Merged
bendbennett
added a commit
that referenced
this issue
Sep 4, 2023
…er, or resource name as package name (#20)
bendbennett
added a commit
that referenced
this issue
Sep 4, 2023
bendbennett
added a commit
that referenced
this issue
Sep 5, 2023
…kageName flag is not specified (#20)
bendbennett
added a commit
that referenced
this issue
Sep 5, 2023
… "example" to highlight the default behaviour for directory and package generation (#20)
bendbennett
added a commit
that referenced
this issue
Sep 7, 2023
… and resource (#39) * Default to empty string for package flag, and use data source, provider, or resource name as package name (#20) * Adding test coverage to verify package name can be overridden by supplying --package flag (#20) * Add generated code to separate directories (#20) * Only create directory and package per data source and resource if packageName flag is not specified (#20) * Changing the name of data source, provider and resource in ir.json to "example" to highlight the default behaviour for directory and package generation (#20) * Adding doc comments (#20)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
During the generation of data models there is the potential for the generated model names to conflict. There are at least 2 situations in which this could arise:
Schemas that contain nested attributes
For example, in the case of schemas that contain nested attributes, we could have a situation such as the following in which two list_nested attributes within the intermediate representation contain an attribute with the same name
The generated models have a naming collision:
Data sources, provider and resources that contain nested attributes
An analogous situation could arise with data sources, provider and resources in which the schema contain nested attributes or blocks with the same names.
Possible Solutions
The text was updated successfully, but these errors were encountered: