-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Comment about consistency in Language strings #6341
Comments
I think this should be discussed in the main repository. So that if ever there will be changes there, those will just be cascaded here. |
(Sorry, didn't see it was moved) |
I would like to if possible. |
@tangix if you would like to take a first pass at that we would gratefully review your Pull Request! |
I can work on that. Unfortunately I think this change will break backward compatibility when tests checking the error message will start to fail, please advise. Personally I prefer For example:
and when separated by colon:
Also, I think errors should be written like this: |
I'm good with all those opinions. I think the consistency is more important than the particular syntax (though I would probably do pretty much as you have suggested). Language files and contents are intentionally internal, so no concerns about breaking changes. If a test is verifying a language response it should be using the function, not the text directly: // this:
$this->assertSame(lang('Foo.bar', ['bam']), $result);
// not this:
$this->assertSame('Foo bar had a "bam"', $result); |
I think if the value (may) contains a space, it is better to quote with
|
I'm both in favor. |
Closed by #6474 |
👏 |
Just want to comment on the use of
{0}
in the strings:there are multiple ways of showing for example filenames in the messages:
"{0}"
,({0})
,`{0}`
or simply without quotes or parenthesis{0}
Should maybe be standardized to one format?
The text was updated successfully, but these errors were encountered: