-
Notifications
You must be signed in to change notification settings - Fork 175
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
Rename quatUser & quatPassword to something more descriptive #5785
Conversation
The other username and password are also for the database so I don't know if this name is much better. nothing better is coming to mind right now though. |
Also I think this should probably go to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think since it's within a <database>
parent tag adminUser
and adminPassword
would be better for the reasons @johnsaigle mentioned.
Looks good, thanks for the cleanup! |
162316c
to
a10aa50
Compare
@driusan @johnsaigle I rebased to major. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
make the purpose of this user clear. After resolving conflict.
Adding tags because projects will need to update existing settings |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suspect there might be other references straggling around that we won't find until release testing, but this is still a good start to fixing this long-standing annoyance..
Brief summary of changes
The quatUser is now dbUser and the quatPassword is now dbPassword.
Links to related tickets (GitHub, Redmine, ...)