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.

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

OData Metadata file Code is not in line with model options Code conventions #21

Closed
harmen-xb opened this issue Jun 7, 2023 · 1 comment · Fixed by #23
Closed

OData Metadata file Code is not in line with model options Code conventions #21

harmen-xb opened this issue Jun 7, 2023 · 1 comment · Fixed by #23
Labels
enhancement New feature or request

Comments

@harmen-xb
Copy link
Contributor

harmen-xb commented Jun 7, 2023

The Code of the OData Metadata file is 'ODATA_METADATA', but the model options naming conventions the Code is set to Mixed Case. So when applying the naving conventions to all objects the menu option to update a model disappears.

I think it's better to update the name convention for this file.

Note: This does require existing models to be update with the new Code,

@harmen-xb harmen-xb added the enhancement New feature or request label Jun 7, 2023
harmen-xb added a commit that referenced this issue Aug 2, 2023
Implemented debug mode using PowerDesigner variable and updated README.
@harmen-xb
Copy link
Contributor Author

Change the Code to be Mixed Case. When an existing model still has the uppercase Code it will automatically be updated in the next model update (since finding the metadata file is now case insensitive).

@harmen-xb harmen-xb linked a pull request Aug 2, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant