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

Use correct neither…nor construction #176

Open
wants to merge 1 commit into
base: gh-pages
Choose a base branch
from
Open

Use correct neither…nor construction #176

wants to merge 1 commit into from

Conversation

getaaron
Copy link

"neither fixtures or factories" is grammatically incorrect. This PR changes the clause to "neither fixtures nor factories".

An alternative, but more intrusive, fix would be to change the whole sentence to "When talking about unit tests the best practice is to avoid fixtures and factories entirely."

http://thewritepractice.com/how-to-use-either-neither-or-and-nor-correctly/

@onebree
Copy link
Contributor

onebree commented Mar 15, 2016

@getaaron I am for changing the sentence. What do you think about this:

It's important to note that when regarding unit tests, it is best practice to avoid factories and fixtures altogether.

If you know another language, please add the fixed translation to this PR.

This PR will be merged after checking the progress with the new translations effort.

@johana-star
Copy link

Is there anything preventing this work from being merged?

@onebree
Copy link
Contributor

onebree commented Jan 3, 2018

@strand It's been a while, but IIRC I think I wanted to make sure all appropriate translations were added so the change happens everywhere, as necessary. IDK though if other languages would need this kind of change though.

@johana-star
Copy link

🤔 I think we should avoid blocking work from being merged until translations of that work is available. I'm not certain what practice one should use to ensure translations stay in sync.

Perhaps we could use a comment to indicate which SHA or tag the translation is based off of, and then every update to a translation would be able to translate just the changes introduced between the tag and the current version? That way the translations could be updated not on a change level, but a release or a version level, reducing the amount of back-and-forth communication we need to have with translator volunteers.

Copy link

@kbrock kbrock left a comment

Choose a reason for hiding this comment

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

LGTM

@kbrock
Copy link

kbrock commented Oct 2, 2019

The neither/nor construct is English only.
Spanish for one has constructs around not that would be a double negative in English.

I agree, this looks good

@getaaron
Copy link
Author

Let’s merge it! 😀

@akz92
Copy link
Member

akz92 commented Mar 20, 2020

Thanks for you help @getaaron! Could you please update this PR to use the new _i18n/*.yml structure? There's an issue open addressing this change if you want to join: #214

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants