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

[engine] Fix typo for database function name #990

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

Conversation

0ffer
Copy link
Contributor

@0ffer 0ffer commented Jan 14, 2025

Changes introduced with this PR

Just fix small typo in database function name.

Are you the owner of the code you are sending in, or do you have permission of the owner?

[y/n]

yes

@dupondje dupondje requested review from dupondje and removed request for emesika and mwperina January 14, 2025 16:31
Copy link
Member

@dupondje dupondje left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the change.

Could you just adjust the commit message?
As this is a change on the 'core' component, can you use.

core: fix typo in RoleDao

All our commits are prepended by the component, then a :, and some small info.
Check the history of the touched files to have some examples :)
This way we keep the commit messages a bit the same style. Otherwise it will become a mess.

And then some small message in the commit message?

From the initiation of the project there was typo in the database function with name 'GetRolsByid'.
This changes just rename this function to more correct 'GetRoleByid' and change it at the calling side in the DAO layer.

Signed-off-by: Stanislav Melnichuk <[email protected]>
@0ffer
Copy link
Contributor Author

0ffer commented Jan 14, 2025

Yep, sorry, I forget about this 🥲
But I read some time ago this file and remember that some formatting needed.
https://github.com/oVirt/ovirt-engine/blob/master/config/engine-commit-template.txt

I fixed message for the commit.

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

Successfully merging this pull request may close these issues.

2 participants