Skip to content

[Doc FR]: guides/*.md translated. #159

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

Merged
merged 5 commits into from
Nov 22, 2017
Merged

[Doc FR]: guides/*.md translated. #159

merged 5 commits into from
Nov 22, 2017

Conversation

MachinisteWeb
Copy link
Contributor

Hi ! We are Vuejs-FR team and we translated all Vue documentation in french. We have finish to translate the Guides part of vue-test-utils documentation.

We also have added a message in API page not still translated to invite anyone want to help us with the translation.

Feel free to merge this PR now (really useful because all part already translated will be availlable or wait we have translate all API part too.

@eddyerburgh
Copy link
Member

I'll wait until the API is translated. Looks good so far 😀

@MachinisteWeb
Copy link
Contributor Author

OK!

@eddyerburgh
Copy link
Member

@posva @Akryum Would either of you be able to review this PR?

@MachinisteWeb
Copy link
Contributor Author

Just focus on files under guides/, I will add « english » mention in others files before merge.

Copy link
Member

@posva posva left a comment

Choose a reason for hiding this comment

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

Thanks a lot @haeresis
@eddyerburgh just so you know, the idea here is to progressively translate the docs, so @haeresis will create more PRs as he translates the docs. Right now, only /guides is translated, the rest is left in english with a little notice in the top ( I think he already said it, but repeating just in case 😆 )

@@ -0,0 +1,70 @@
## Table of Contents
Copy link
Member

Choose a reason for hiding this comment

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

Je penseque ça serait bien d'avoir le fichier entier traduit

* [Guides](guides/README.md)
* [Commencer](guides/getting-started.md)
* [Astuces](guides/common-tips.md)
* [Mouse, Key and other DOM Events (EN)](guides/dom-events.md)
Copy link
Member

Choose a reason for hiding this comment

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

idem


Un lanceur de tests est un programme qui lance des tests (et oui !).

Il y a un nombre conséquent de lanceurs de tests JavaScript et `vue-test-utils` fonctionne avec tous. `vue-test-utils` est agnostique en termne de lanceurs de tests.
Copy link
Member

Choose a reason for hiding this comment

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

terme


Dans des tests unitaires, on souhaite s'intéresser au composant qui est en train d'être testé comme une unité isolée et ainsi éviter de s'assurer du bon comportement des composants enfants.

De plus, pour les composants qui contiennent beaucoup de composants enfant, l'intégralité de l'arbre de rendu peut être énorme. Répétitivement rendre tous les composants pourrait réduire la vitesse de nos tests.
Copy link
Member

Choose a reason for hiding this comment

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

composants enfants, non?


#### Externaliser les dépendances npm

Dans nos tests, nous allons surement importer un nombre conséquent de dépendances npm, certaines d'entre elles n'ont pas été conçues pour une utilisation dans un navigateur et ne peuvent être empaquetées par webpack. Il faut aussi considérer qu'externaliser les dépendances augmente énormément la vitesse de lancement des tests. On peut externaliser toutes les dépendances npm avec `webpack-node-externals -externals` :
Copy link
Member

Choose a reason for hiding this comment

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

un petit -externals en trop

}
})

wrapper.vm.$router // /un/super/chemin
Copy link
Member

Choose a reason for hiding this comment

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

@eddyerburgh I think there's a typo here, shouldn't et be wrapper.vm.$route.path?

Copy link
Member

Choose a reason for hiding this comment

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

Yep you're correct 😀

Signed-off-by: Bruno Lesieur <[email protected]>
@MachinisteWeb
Copy link
Contributor Author

Thanks a lot to you @posva ;)

Guide part up to date. We contunue api and new components part.

@eddyerburgh eddyerburgh merged commit b5e3ac2 into vuejs:dev Nov 22, 2017
@eddyerburgh
Copy link
Member

Great work guys 🙌

@MachinisteWeb
Copy link
Contributor Author

\o/

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

Successfully merging this pull request may close these issues.

3 participants