-
Notifications
You must be signed in to change notification settings - Fork 40
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
Checks for start and end of parsing #16
Comments
Yeah this makes sense. Pleasw make a PR :)
fre. 8. feb. 2019 kl. 12:31 skrev Johannes Deml <notifications@github.com>:
… I just had the problem that my localization filw was not parsed anymore,
even though I just added three simple strings to the file. After quite a
while I found the problem: One added ID was "ENDSCREEN_BUTTON", which
triggered if(key.StartsWith("END")) in LocalizationImporter.cs.
I think another convention than checking if the string starts with END
would be benefitial for the project. I suggest to check for an equals
instead of using StartsWith(). To stay consistent I propose to do this
change for the start as well. So the code would change to
if (!canBegin)
{
if (key == "Polyglot" || key == "PolyMaster" || key == "BEGIN")
{
canBegin = true;
}
continue;
}
if (key=="END")
{
break;
}
If this is in the interest of those involved I would create a PR for it :)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#16>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAitDWvcOTbzjVnGm8B1PQJEV6KnFQHYks5vLWAYgaJpZM4avIil>
.
|
Awesome, thanks for the quick response! ❤ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I just had the problem that my localization filw was not parsed anymore, even though I just added three simple strings to the file. After quite a while I found the problem: One added ID was "ENDSCREEN_BUTTON", which triggered
if(key.StartsWith("END"))
in LocalizationImporter.cs.I think another convention than checking if the string starts with END would be benefitial for the project. I suggest to check for an equals instead of using
StartsWith()
. To stay consistent I propose to do this change for the start as well. So the code would change toIf this is in the interest of those involved I would create a PR for it :)
The text was updated successfully, but these errors were encountered: