Codechange: Spell 'Viewport' consistently#8260
Conversation
|
Nothing will break as far as I know, go ahead and do the strings as well :) |
It won't break the translation/localisation system? |
|
Nah. Probably. |
|
Translations should be safe if everything match. The translation system always reads the updated strings. |
I thought that only applied to translations? What we are proposing here is to change the symbolic identifiers; things would break horribly if they weren't consistent all the way through, yeah? |
17eead3 to
6dcde46
Compare
6dcde46 to
bea33f1
Compare
bea33f1 to
96937df
Compare
|
Oops, didn‘t need to rebase this one. Sorry about that. (I wonder if I can undo it? 🤔) |
96937df to
bea33f1
Compare
|
Only by (effectively) rebasing again. Why would you want to anyway? |
Habit, I guess. Most of my PRs seem to end up conflicting with each other one way or another. |
bea33f1 to
b823268
Compare
LordAro
left a comment
There was a problem hiding this comment.
Not especially waiting on anything
b823268 to
f2ba109
Compare
Some places in the codebase misspell 'Viewport' as 'ViewPort' or 'view_port'. This patch makes everything consistent.
f2ba109 to
69fdaa5
Compare
Some places in the codebase misspell 'Viewport' as 'ViewPort' or 'view_port'.
This patch makes everything consistent.
There are several strings that are named
VIEW_PORTand/orVIEWPORT. I have left these alone because I do not know what will break.