From 4519a3a954b8277933258c6ed3986a25c5dfa573 Mon Sep 17 00:00:00 2001 From: Raz Luvaton Date: Mon, 19 Jul 2021 23:31:12 +0300 Subject: [PATCH] Replace github links that point to this repo with relative links --- .operations/CONTRIBUTING.md | 4 ++-- .operations/operations-manual.md | 2 +- .operations/writing-guidelines.chinese.md | 2 +- .operations/writing-guidelines.french.md | 2 +- .operations/writing-guidelines.indonesia.md | 4 ++-- .operations/writing-guidelines.japanese.md | 2 +- .operations/writing-guidelines.md | 2 +- .operations/writing-guidelines.polish.md | 2 +- .operations/writing-guidelines.russian.md | 2 +- README.french.md | 2 +- README.md | 2 +- sections/errorhandling/apmproducts.basque.md | 4 ++-- sections/errorhandling/apmproducts.brazilian-portuguese.md | 4 ++-- sections/errorhandling/apmproducts.chinese.md | 4 ++-- sections/errorhandling/apmproducts.french.md | 4 ++-- sections/errorhandling/apmproducts.japanese.md | 4 ++-- sections/errorhandling/apmproducts.korean.md | 4 ++-- sections/errorhandling/apmproducts.md | 4 ++-- sections/errorhandling/apmproducts.polish.md | 4 ++-- sections/errorhandling/apmproducts.russian.md | 4 ++-- sections/errorhandling/centralizedhandling.french.md | 2 +- sections/errorhandling/centralizedhandling.md | 2 +- sections/errorhandling/documentingusingswagger.basque.md | 2 +- .../documentingusingswagger.brazilian-portuguese.md | 2 +- sections/errorhandling/documentingusingswagger.chinese.md | 2 +- sections/errorhandling/documentingusingswagger.french.md | 2 +- sections/errorhandling/documentingusingswagger.japanese.md | 2 +- sections/errorhandling/documentingusingswagger.korean.md | 2 +- sections/errorhandling/documentingusingswagger.md | 2 +- sections/errorhandling/documentingusingswagger.polish.md | 2 +- sections/errorhandling/documentingusingswagger.russian.md | 2 +- sections/projectstructre/breakintcomponents.basque.md | 4 ++-- .../breakintcomponents.brazilian-portuguese.md | 4 ++-- sections/projectstructre/breakintcomponents.chinese.md | 4 ++-- sections/projectstructre/breakintcomponents.french.md | 4 ++-- sections/projectstructre/breakintcomponents.japanese.md | 4 ++-- sections/projectstructre/breakintcomponents.korean.md | 4 ++-- sections/projectstructre/breakintcomponents.md | 4 ++-- sections/projectstructre/breakintcomponents.polish.md | 4 ++-- sections/projectstructre/breakintcomponents.russian.md | 4 ++-- sections/projectstructre/createlayers.basque.md | 4 ++-- .../projectstructre/createlayers.brazilian-portuguese.md | 4 ++-- sections/projectstructre/createlayers.chinese.md | 4 ++-- sections/projectstructre/createlayers.french.md | 4 ++-- sections/projectstructre/createlayers.japanese.md | 4 ++-- sections/projectstructre/createlayers.korean.md | 4 ++-- sections/projectstructre/createlayers.md | 4 ++-- sections/projectstructre/createlayers.polish.md | 4 ++-- sections/projectstructre/createlayers.russian.md | 4 ++-- sections/projectstructre/thincomponents.chinese.md | 4 ++-- sections/projectstructre/thincomponents.french.md | 4 ++-- sections/projectstructre/thincomponents.japanese.md | 4 ++-- sections/projectstructre/thincomponents.md | 4 ++-- sections/projectstructre/thincomponents.russian.md | 4 ++-- sections/projectstructre/wraputilities.basque.md | 2 +- .../projectstructre/wraputilities.brazilian-portuguese.md | 2 +- sections/projectstructre/wraputilities.chinese.md | 2 +- sections/projectstructre/wraputilities.french.md | 2 +- sections/projectstructre/wraputilities.japanese.md | 2 +- sections/projectstructre/wraputilities.korean.md | 2 +- sections/projectstructre/wraputilities.md | 2 +- sections/projectstructre/wraputilities.polish.md | 2 +- sections/projectstructre/wraputilities.russian.md | 2 +- sections/template.basque.md | 6 +++--- sections/template.md | 6 +++--- sections/testingandquality/3-parts-in-name.basque.md | 2 +- .../3-parts-in-name.brazilian-portuguese.md | 4 ++-- sections/testingandquality/3-parts-in-name.french.md | 4 ++-- sections/testingandquality/3-parts-in-name.japanese.md | 4 ++-- sections/testingandquality/3-parts-in-name.md | 2 +- sections/testingandquality/3-parts-in-name.polish.md | 2 +- sections/testingandquality/3-parts-in-name.russian.md | 4 ++-- sections/testingandquality/bumpversion.japanese.md | 2 +- sections/testingandquality/bumpversion.md | 2 +- sections/testingandquality/citools.basque.md | 4 ++-- sections/testingandquality/citools.brazilian-portuguese.md | 4 ++-- sections/testingandquality/citools.chinese.md | 4 ++-- sections/testingandquality/citools.french.md | 4 ++-- sections/testingandquality/citools.japanese.md | 4 ++-- sections/testingandquality/citools.korean.md | 4 ++-- sections/testingandquality/citools.md | 4 ++-- sections/testingandquality/citools.polish.md | 4 ++-- sections/testingandquality/citools.russian.md | 4 ++-- sections/testingandquality/refactoring.basque.md | 6 +++--- .../testingandquality/refactoring.brazilian-portuguese.md | 6 +++--- sections/testingandquality/refactoring.french.md | 6 +++--- sections/testingandquality/refactoring.japanese.md | 6 +++--- sections/testingandquality/refactoring.md | 6 +++--- sections/testingandquality/refactoring.polish.md | 6 +++--- sections/testingandquality/refactoring.russian.md | 6 +++--- 90 files changed, 155 insertions(+), 155 deletions(-) diff --git a/.operations/CONTRIBUTING.md b/.operations/CONTRIBUTING.md index 04139cc6f..55f9435ed 100644 --- a/.operations/CONTRIBUTING.md +++ b/.operations/CONTRIBUTING.md @@ -10,11 +10,11 @@ We recognize that being professional and kind are the same thing and strive to m ### Maintenance work -Our operations manual [can be found here](https://github.com/goldbergyoni/nodebestpractices/blob/master/.operations/operations-manual.md) +Our operations manual [can be found here](/.operations/operations-manual.md) ### Writing guidelines -Our content writing guidelines [can be found here](https://github.com/goldbergyoni/nodebestpractices/blob/master/.operations/writing-guidelines.md) +Our content writing guidelines [can be found here](/.operations/writing-guidelines.md) ### Handling issues and PRs diff --git a/.operations/operations-manual.md b/.operations/operations-manual.md index ee932284d..3de9e7c58 100644 --- a/.operations/operations-manual.md +++ b/.operations/operations-manual.md @@ -8,7 +8,7 @@ In a nutshell, every issue and PR should get tagged by one of our core team and There is no specific person on call who assigns inquiries rather we count on our core team to visit almost everyday and assign issues/PR - this way, the workflow is not depend upon any specific person rather on our entire team. -Any new content should conform to our [writing guidelines](https://github.com/goldbergyoni/nodebestpractices/blob/master/.operations/writing-guidelines.md) +Any new content should conform to our [writing guidelines](/.operations/writing-guidelines.md) ## Monthly maintenance diff --git a/.operations/writing-guidelines.chinese.md b/.operations/writing-guidelines.chinese.md index 695658988..99976ee65 100644 --- a/.operations/writing-guidelines.chinese.md +++ b/.operations/writing-guidelines.chinese.md @@ -16,7 +16,7 @@ ## 4. 一致的格式 -内容是使用固定模板显示的。任何新的内容都必须遵守这一模板。如果希望添加新项目符号，请从现有项目符号复制项目符号格式，并将其扩展以满足您的需要。有关其他信息，请查看[模版](https://github.com/goldbergyoni/nodebestpractices/blob/master/sections/template.md) +内容是使用固定模板显示的。任何新的内容都必须遵守这一模板。如果希望添加新项目符号，请从现有项目符号复制项目符号格式，并将其扩展以满足您的需要。有关其他信息，请查看[模版](/sections/template.md) ## 5. Node.js 相关 diff --git a/.operations/writing-guidelines.french.md b/.operations/writing-guidelines.french.md index 663a82ee8..063951117 100644 --- a/.operations/writing-guidelines.french.md +++ b/.operations/writing-guidelines.french.md @@ -16,7 +16,7 @@ En plus d'être d'une grande fiabilité et d'une grande qualité rédactionnelle ## 4. Formatage cohérent -Le contenu est présenté à l'aide de modèles prédéfinis. Tout contenu futur doit être conforme au même modèle. Si vous souhaitez ajouter de nouveaux points, copiez le format d'un point existant et complétez-le selon vos besoins. Pour plus d'informations, veuillez consulter [ce modèle](https://github.com/goldbergyoni/nodebestpractices/blob/master/sections/template.md). +Le contenu est présenté à l'aide de modèles prédéfinis. Tout contenu futur doit être conforme au même modèle. Si vous souhaitez ajouter de nouveaux points, copiez le format d'un point existant et complétez-le selon vos besoins. Pour plus d'informations, veuillez consulter [ce modèle](/sections/template.md). ## 5. C'est à propos de Node.js diff --git a/.operations/writing-guidelines.indonesia.md b/.operations/writing-guidelines.indonesia.md index 3b65f7580..d33359121 100644 --- a/.operations/writing-guidelines.indonesia.md +++ b/.operations/writing-guidelines.indonesia.md @@ -16,7 +16,7 @@ Selain konten yang sangat diedit dan dapat diandalkan, membaca sekilas konten ju ## 4. Pemformatan yang konsisten -Konten disajikan menggunakan templat tetap. Setiap konten di masa mendatang harus sesuai dengan template yang sama. Jika Anda ingin menambahkan poin baru, salin format poin dari poin yang ada dan kembangkan sesuai kebutuhan Anda. Untuk informasi tambahan, silakan lihat [template ini] (https://github.com/goldbergyoni/nodebestpractices/blob/master/sections/template.md). +Konten disajikan menggunakan templat tetap. Setiap konten di masa mendatang harus sesuai dengan template yang sama. Jika Anda ingin menambahkan poin baru, salin format poin dari poin yang ada dan kembangkan sesuai kebutuhan Anda. Untuk informasi tambahan, silakan lihat [template ini] (/sections/template.md). ## 5. Ini Tentang Node.js @@ -28,4 +28,4 @@ Terkadang berguna untuk memasukkan nama vendor yang dapat mengatasi tantangan da - Hanya 3 vendor teratas yang disarankan - vendor yang muncul di 3 hasil teratas dari mesin pencari (Google atau GitHub diurutkan berdasarkan popularitas) untuk kata kunci relevan tertentu dapat dimasukkan dalam rekomendasi kami. - Jika ini adalah paket npm, itu juga harus diunduh setidaknya rata-rata 750 kali sehari. -- Jika ini adalah proyek sumber terbuka, itu harus diperbarui setidaknya sekali dalam 6 bulan terakhir. \ No newline at end of file +- Jika ini adalah proyek sumber terbuka, itu harus diperbarui setidaknya sekali dalam 6 bulan terakhir. diff --git a/.operations/writing-guidelines.japanese.md b/.operations/writing-guidelines.japanese.md index 155b6bafa..23961a79d 100644 --- a/.operations/writing-guidelines.japanese.md +++ b/.operations/writing-guidelines.japanese.md @@ -16,7 +16,7 @@ Apart from the content being greatly edited and reliable, skimming through it sh ## 4. Consistent formatting -The content is presented using fixed templates. Any future content must conform to the same template. If you wish to add new bullets copy a bullet format from an existing bullet and extend it to your needs. For additional information please view [this template](https://github.com/goldbergyoni/nodebestpractices/blob/master/sections/template.md). +The content is presented using fixed templates. Any future content must conform to the same template. If you wish to add new bullets copy a bullet format from an existing bullet and extend it to your needs. For additional information please view [this template](/sections/template.md). ## 5. It's About Node.js diff --git a/.operations/writing-guidelines.md b/.operations/writing-guidelines.md index daae6b9cf..633e677a8 100644 --- a/.operations/writing-guidelines.md +++ b/.operations/writing-guidelines.md @@ -16,7 +16,7 @@ Apart from the content being greatly edited and reliable, skimming through it sh ## 4. Consistent formatting -The content is presented using fixed templates. Any future content must conform to the same template. If you wish to add new bullets copy a bullet format from an existing bullet and extend it to your needs. For additional information please view [this template](https://github.com/goldbergyoni/nodebestpractices/blob/master/sections/template.md). +The content is presented using fixed templates. Any future content must conform to the same template. If you wish to add new bullets copy a bullet format from an existing bullet and extend it to your needs. For additional information please view [this template](/sections/template.md). ## 5. It's About Node.js diff --git a/.operations/writing-guidelines.polish.md b/.operations/writing-guidelines.polish.md index 471525ade..bf887c58f 100644 --- a/.operations/writing-guidelines.polish.md +++ b/.operations/writing-guidelines.polish.md @@ -16,7 +16,7 @@ Oprócz tego, że treść jest znacznie edytowana i niezawodna, przeglądanie w ## 4. Spójne formatowanie -Treść jest prezentowana przy użyciu stałych szablonów. Wszelkie przyszłe treści muszą być zgodne z tym samym szablonem. Jeśli chcesz dodać nowe punktory, skopiuj format punktora z istniejącego i rozszerz go do swoich potrzeb. Aby uzyskać dodatkowe informacje, zobacz [ten szablon](https://github.com/goldbergyoni/nodebestpractices/blob/master/sections/template.md). +Treść jest prezentowana przy użyciu stałych szablonów. Wszelkie przyszłe treści muszą być zgodne z tym samym szablonem. Jeśli chcesz dodać nowe punktory, skopiuj format punktora z istniejącego i rozszerz go do swoich potrzeb. Aby uzyskać dodatkowe informacje, zobacz [ten szablon](/sections/template.md). ## 5. To na temat Node.js diff --git a/.operations/writing-guidelines.russian.md b/.operations/writing-guidelines.russian.md index 0ef1389cf..fef632d36 100644 --- a/.operations/writing-guidelines.russian.md +++ b/.operations/writing-guidelines.russian.md @@ -16,7 +16,7 @@ ## 4. Согласованное форматирование -Контент представлен с использованием фиксированных шаблонов. Любое будущее содержание должно соответствовать тому же шаблону. Если вы хотите добавить новые маркеры, скопируйте формат маркера из существующего маркера и расширьте его для своих нужд. Для получения дополнительной информации, пожалуйста, просмотрите [этот шаблон](https://github.com/goldbergyoni/nodebestpractices/blob/master/sections/template.md). +Контент представлен с использованием фиксированных шаблонов. Любое будущее содержание должно соответствовать тому же шаблону. Если вы хотите добавить новые маркеры, скопируйте формат маркера из существующего маркера и расширьте его для своих нужд. Для получения дополнительной информации, пожалуйста, просмотрите [этот шаблон](/sections/template.md). ## 5. Это про Node.js diff --git a/README.french.md b/README.french.md index d75cd56c1..60dc1769d 100644 --- a/README.french.md +++ b/README.french.md @@ -1289,7 +1289,7 @@ Toutes les traductions sont fournies par la communauté. Nous serons heureux de ### Traductions en cours -- ![FR](./assets/flags/FR.png) [Français](https://github.com/goldbergyoni/nodebestpractices/blob/master/README.french.md) ([Discussion](https://github.com/goldbergyoni/nodebestpractices/issues/129)) +- ![FR](./assets/flags/FR.png) [Français](./README.french.md) ([Discussion](https://github.com/goldbergyoni/nodebestpractices/issues/129)) - ![HE](./assets/flags/HE.png) Hébreu ([Discussion](https://github.com/goldbergyoni/nodebestpractices/issues/156)) - ![KR](./assets/flags/KR.png) [Coréen](README.korean.md) - Avec l'aimable autorisation de [Sangbeom Han](https://github.com/uronly14me) ([Discussion](https://github.com/goldbergyoni/nodebestpractices/issues/94)) - ![ES](./assets/flags/ES.png) [Espagnol](https://github.com/goldbergyoni/nodebestpractices/blob/spanish-translation/README.spanish.md) ([Discussion](https://github.com/goldbergyoni/nodebestpractices/issues/95)) diff --git a/README.md b/README.md index a2add32dc..690d1941d 100644 --- a/README.md +++ b/README.md @@ -1289,7 +1289,7 @@ All translations are contributed by the community. We will be happy to get any h ### Translations in progress -- ![FR](./assets/flags/FR.png) [French](https://github.com/goldbergyoni/nodebestpractices/blob/master/README.french.md) ([Discussion](https://github.com/goldbergyoni/nodebestpractices/issues/129)) +- ![FR](./assets/flags/FR.png) [French](./README.french.md) ([Discussion](https://github.com/goldbergyoni/nodebestpractices/issues/129)) - ![HE](./assets/flags/HE.png) Hebrew ([Discussion](https://github.com/goldbergyoni/nodebestpractices/issues/156)) - ![KR](./assets/flags/KR.png) [Korean](README.korean.md) - Courtesy of [Sangbeom Han](https://github.com/uronly14me) ([Discussion](https://github.com/goldbergyoni/nodebestpractices/issues/94)) - ![ES](./assets/flags/ES.png) [Spanish](https://github.com/goldbergyoni/nodebestpractices/blob/spanish-translation/README.spanish.md) ([Discussion](https://github.com/goldbergyoni/nodebestpractices/issues/95)) diff --git a/sections/errorhandling/apmproducts.basque.md b/sections/errorhandling/apmproducts.basque.md index 11e7158c9..0ea3a2126 100644 --- a/sections/errorhandling/apmproducts.basque.md +++ b/sections/errorhandling/apmproducts.basque.md @@ -20,8 +20,8 @@ APM produktuek 3 segmentu nagusi dituzte: ### Adibidea: UpTimeRobot.Com: webguneak monitorizatzeko panela -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/uptimerobot.jpg "Webgune monitorizazio aurreko panela") +![alt text](../../assets/images/uptimerobot.jpg "Webgune monitorizazio aurreko panela") ### Adibidea: AppDynamics.Com: hasieratik amaierarainoko monitorizazioa kode instrumentazioarekin konbinatutakoa -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/app-dynamics-dashboard.png "kode instrumentazioarekin konbinatutako hasieratik amaierarainoko monitorizazioa") +![alt text](../../assets/images/app-dynamics-dashboard.png "kode instrumentazioarekin konbinatutako hasieratik amaierarainoko monitorizazioa") diff --git a/sections/errorhandling/apmproducts.brazilian-portuguese.md b/sections/errorhandling/apmproducts.brazilian-portuguese.md index 1e7b824cb..459e50f10 100644 --- a/sections/errorhandling/apmproducts.brazilian-portuguese.md +++ b/sections/errorhandling/apmproducts.brazilian-portuguese.md @@ -22,7 +22,7 @@ Os produtos APM constituem 3 segmentos principais: ### Exemplo: UpTimeRobot.Com - Painel de monitoramento de site -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/uptimerobot.jpg "Painel de monitoramento de sites") +![alt text](../../assets/images/uptimerobot.jpg "Painel de monitoramento de sites") ### Example: AppDynamics.Com – monitoramento de ponta a ponta combinado com instrumentação de código -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/app-dynamics-dashboard.png "monitoramento de ponta a ponta combinado com instrumentação de código") +![alt text](../../assets/images/app-dynamics-dashboard.png "monitoramento de ponta a ponta combinado com instrumentação de código") diff --git a/sections/errorhandling/apmproducts.chinese.md b/sections/errorhandling/apmproducts.chinese.md index 8803f2791..0777b7359 100644 --- a/sections/errorhandling/apmproducts.chinese.md +++ b/sections/errorhandling/apmproducts.chinese.md @@ -21,7 +21,7 @@ APM 产品由3个主要部分构成: ### 示例: UpTimeRobot.Com – 网站监控仪表板 -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/uptimerobot.jpg "Website monitoring dashboard") +![alt text](../../assets/images/uptimerobot.jpg "Website monitoring dashboard") ### 示例: AppDynamics.Com – 与代码检测结合的端到端监视 -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/app-dynamics-dashboard.png "end to end monitoring combined with code instrumentation") +![alt text](../../assets/images/app-dynamics-dashboard.png "end to end monitoring combined with code instrumentation") diff --git a/sections/errorhandling/apmproducts.french.md b/sections/errorhandling/apmproducts.french.md index 1d4f206fd..bfe5f5916 100644 --- a/sections/errorhandling/apmproducts.french.md +++ b/sections/errorhandling/apmproducts.french.md @@ -22,7 +22,7 @@ Les produits APM regroupent 3 pôles principaux : ### Exemple : UpTimeRobot.Com - Tableau de bord de surveillance de site Web -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/uptimerobot.jpg "Tableau de bord de surveillance de site Web") +![alt text](../../assets/images/uptimerobot.jpg "Tableau de bord de surveillance de site Web") ### Exemple : AppDynamics.Com - Surveillance de bout en bout combinée à une instrumentation de code -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/app-dynamics-dashboard.png "Surveillance de bout en bout combinée à une instrumentation de code") +![alt text](../../assets/images/app-dynamics-dashboard.png "Surveillance de bout en bout combinée à une instrumentation de code") diff --git a/sections/errorhandling/apmproducts.japanese.md b/sections/errorhandling/apmproducts.japanese.md index 34370867c..5e8b56f80 100644 --- a/sections/errorhandling/apmproducts.japanese.md +++ b/sections/errorhandling/apmproducts.japanese.md @@ -22,7 +22,7 @@ APM 製品は 3 つの主要なセグメントを構成しています: ### 例: UpTimeRobot.Com – ウェブサイトモニタリングダッシュボード -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/uptimerobot.jpg "ウェブサイトモニタリングダッシュボード") +![alt text](../../assets/images/uptimerobot.jpg "ウェブサイトモニタリングダッシュボード") ### 例: AppDynamics.Com – コード計測が統合されたエンドツーエンドモニタリング -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/app-dynamics-dashboard.png "コード計測が統合されたエンドツーエンドモニタリング") +![alt text](../../assets/images/app-dynamics-dashboard.png "コード計測が統合されたエンドツーエンドモニタリング") diff --git a/sections/errorhandling/apmproducts.korean.md b/sections/errorhandling/apmproducts.korean.md index ad5081797..fd4ae438e 100644 --- a/sections/errorhandling/apmproducts.korean.md +++ b/sections/errorhandling/apmproducts.korean.md @@ -22,7 +22,7 @@ APM products constitute 3 major segments: ### Example: UpTimeRobot.Com – Website monitoring dashboard -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/uptimerobot.jpg "Website monitoring dashboard") +![alt text](../../assets/images/uptimerobot.jpg "Website monitoring dashboard") ### Example: AppDynamics.Com – end to end monitoring combined with code instrumentation -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/app-dynamics-dashboard.png "end to end monitoring combined with code instrumentation") +![alt text](../../assets/images/app-dynamics-dashboard.png "end to end monitoring combined with code instrumentation") diff --git a/sections/errorhandling/apmproducts.md b/sections/errorhandling/apmproducts.md index 5f302168d..ae6fc82ec 100644 --- a/sections/errorhandling/apmproducts.md +++ b/sections/errorhandling/apmproducts.md @@ -22,7 +22,7 @@ APM products constitute 3 major segments: ### Example: UpTimeRobot.Com – Website monitoring dashboard -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/uptimerobot.jpg "Website monitoring dashboard") +![alt text](../../assets/images/uptimerobot.jpg "Website monitoring dashboard") ### Example: AppDynamics.Com – end to end monitoring combined with code instrumentation -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/app-dynamics-dashboard.png "end to end monitoring combined with code instrumentation") +![alt text](../../assets/images/app-dynamics-dashboard.png "end to end monitoring combined with code instrumentation") diff --git a/sections/errorhandling/apmproducts.polish.md b/sections/errorhandling/apmproducts.polish.md index a53a4b176..2a10799a8 100644 --- a/sections/errorhandling/apmproducts.polish.md +++ b/sections/errorhandling/apmproducts.polish.md @@ -22,7 +22,7 @@ Produkty APM stanowią 3 główne segmenty: ### Przykład: UpTimeRobot.Com – Website monitoring dashboard -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/uptimerobot.jpg "Website monitoring dashboard") +![alt text](../../assets/images/uptimerobot.jpg "Website monitoring dashboard") ### Przykład: AppDynamics.Com – end to end monitoring combined with code instrumentation -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/app-dynamics-dashboard.png "end to end monitoring combined with code instrumentation") +![alt text](../../assets/images/app-dynamics-dashboard.png "end to end monitoring combined with code instrumentation") diff --git a/sections/errorhandling/apmproducts.russian.md b/sections/errorhandling/apmproducts.russian.md index 242b6786c..e4c23d814 100644 --- a/sections/errorhandling/apmproducts.russian.md +++ b/sections/errorhandling/apmproducts.russian.md @@ -22,7 +22,7 @@ ### Пример: UpTimeRobot.Com - панель мониторинга сайта -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/uptimerobot.jpg "Панель мониторинга сайта") +![alt text](../../assets/images/uptimerobot.jpg "Панель мониторинга сайта") ### Пример: AppDynamics.Com – сквозной мониторинг в сочетании с инструментарием кода -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/app-dynamics-dashboard.png "Сквозной мониторинг в сочетании с инструментарием кода") +![alt text](../../assets/images/app-dynamics-dashboard.png "Сквозной мониторинг в сочетании с инструментарием кода") diff --git a/sections/errorhandling/centralizedhandling.french.md b/sections/errorhandling/centralizedhandling.french.md index 4dfbb73da..ca1f2849a 100644 --- a/sections/errorhandling/centralizedhandling.french.md +++ b/sections/errorhandling/centralizedhandling.french.md @@ -154,7 +154,7 @@ app.use((err: Error, req: Request, res: Response, next: NextFunction) => { ### Illustration : Les acteurs et le flux du traitement des erreurs -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/error-handling-flow.png "Flux de traitement des erreurs") +![alt text](../../assets/images/error-handling-flow.png "Flux de traitement des erreurs") ### Citation de blog : « Parfois, les niveaux inférieurs ne peuvent rien faire d'utile, sauf propager l'erreur à leur appelant » diff --git a/sections/errorhandling/centralizedhandling.md b/sections/errorhandling/centralizedhandling.md index b463e7a9f..7a8f7a6d6 100644 --- a/sections/errorhandling/centralizedhandling.md +++ b/sections/errorhandling/centralizedhandling.md @@ -154,7 +154,7 @@ app.use((err: Error, req: Request, res: Response, next: NextFunction) => { ### Illustration: The error handling actors and flow -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/error-handling-flow.png "Error handling flow") +![alt text](../../assets/images/error-handling-flow.png "Error handling flow") ### Blog Quote: "Sometimes lower levels can’t do anything useful except propagate the error to their caller" diff --git a/sections/errorhandling/documentingusingswagger.basque.md b/sections/errorhandling/documentingusingswagger.basque.md index 8a2bce81a..e88ba2e41 100644 --- a/sections/errorhandling/documentingusingswagger.basque.md +++ b/sections/errorhandling/documentingusingswagger.basque.md @@ -47,4 +47,4 @@ Joyent blogeko “Node.js erregistratzea“ hitz gako bati esker sailkatua ### Tresna erabilgarria: Swagger Online Dokumentazio Sortzailea -![Swagger API Eskema](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/swaggerDoc.png "APIen errore kudeaketa") +![Swagger API Eskema](../../assets/images/swaggerDoc.png "APIen errore kudeaketa") diff --git a/sections/errorhandling/documentingusingswagger.brazilian-portuguese.md b/sections/errorhandling/documentingusingswagger.brazilian-portuguese.md index 4af6a9890..781337b42 100644 --- a/sections/errorhandling/documentingusingswagger.brazilian-portuguese.md +++ b/sections/errorhandling/documentingusingswagger.brazilian-portuguese.md @@ -49,4 +49,4 @@ Do blog Joyent, classificado como 1 para as palavras-chave “Node.js logging” ### Ferramenta Útil: Swagger Criação de Documentação Online -![Swagger API Scheme](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/swaggerDoc.png "lidando com erros API") +![Swagger API Scheme](../../assets/images/swaggerDoc.png "lidando com erros API") diff --git a/sections/errorhandling/documentingusingswagger.chinese.md b/sections/errorhandling/documentingusingswagger.chinese.md index 5d3998ac1..3cf8cc0e3 100644 --- a/sections/errorhandling/documentingusingswagger.chinese.md +++ b/sections/errorhandling/documentingusingswagger.chinese.md @@ -13,4 +13,4 @@ REST API使用HTTP代码返回结果, API用户不仅绝对需要了解API schem ### 有用的工具: Swagger 在线文档创建工具 -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/swaggerDoc.png "API error handling") \ No newline at end of file +![alt text](../../assets/images/swaggerDoc.png "API error handling") diff --git a/sections/errorhandling/documentingusingswagger.french.md b/sections/errorhandling/documentingusingswagger.french.md index 13f407951..0b57ce6d3 100644 --- a/sections/errorhandling/documentingusingswagger.french.md +++ b/sections/errorhandling/documentingusingswagger.french.md @@ -49,4 +49,4 @@ Extrait du blog de Joyent classé en 1ere position pour les mots clés “Node.j ### Outil utile : créateur de documentation en ligne Swagger -![Schéma d'API Swagger](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/swaggerDoc.png "Gestion des erreurs de l'API") +![Schéma d'API Swagger](../../assets/images/swaggerDoc.png "Gestion des erreurs de l'API") diff --git a/sections/errorhandling/documentingusingswagger.japanese.md b/sections/errorhandling/documentingusingswagger.japanese.md index 861add999..10882d198 100644 --- a/sections/errorhandling/documentingusingswagger.japanese.md +++ b/sections/errorhandling/documentingusingswagger.japanese.md @@ -49,4 +49,4 @@ REST API は HTTP ステータスコードを利用して結果を返します ### 便利ツール: Swagger Online Documentation Creator -![Swagger API スキーマ](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/swaggerDoc.png "API エラー処理") +![Swagger API スキーマ](../../assets/images/swaggerDoc.png "API エラー処理") diff --git a/sections/errorhandling/documentingusingswagger.korean.md b/sections/errorhandling/documentingusingswagger.korean.md index 3341b0c13..a101e668a 100644 --- a/sections/errorhandling/documentingusingswagger.korean.md +++ b/sections/errorhandling/documentingusingswagger.korean.md @@ -49,4 +49,4 @@ From the blog Joyent, ranked 1 for the keywords “Node.js logging” ### Useful Tool: Swagger Online Documentation Creator -![Swagger API Scheme](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/swaggerDoc.png "API error handling") +![Swagger API Scheme](../../assets/images/swaggerDoc.png "API error handling") diff --git a/sections/errorhandling/documentingusingswagger.md b/sections/errorhandling/documentingusingswagger.md index b91e7d05d..836f07364 100644 --- a/sections/errorhandling/documentingusingswagger.md +++ b/sections/errorhandling/documentingusingswagger.md @@ -49,4 +49,4 @@ From the blog Joyent, ranked 1 for the keywords “Node.js logging” ### Useful Tool: Swagger Online Documentation Creator -![Swagger API Scheme](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/swaggerDoc.png "API error handling") +![Swagger API Scheme](../../assets/images/swaggerDoc.png "API error handling") diff --git a/sections/errorhandling/documentingusingswagger.polish.md b/sections/errorhandling/documentingusingswagger.polish.md index e274fea45..b6f1dfcd8 100644 --- a/sections/errorhandling/documentingusingswagger.polish.md +++ b/sections/errorhandling/documentingusingswagger.polish.md @@ -49,4 +49,4 @@ Z bloga Joyent, w rankingu 1 dla słów kluczowych “Node.js logging” ### Przydatne narzędzie: Swagger Online Documentation Creator -![Swagger API Scheme](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/swaggerDoc.png "API error handling") +![Swagger API Scheme](../../assets/images/swaggerDoc.png "API error handling") diff --git a/sections/errorhandling/documentingusingswagger.russian.md b/sections/errorhandling/documentingusingswagger.russian.md index 2086e312f..f225e3ca8 100644 --- a/sections/errorhandling/documentingusingswagger.russian.md +++ b/sections/errorhandling/documentingusingswagger.russian.md @@ -49,4 +49,4 @@ API-интерфейсы REST возвращают результаты с ис ### Полезный инструмент: Swagger Online Documentation Creator -![Swagger API Scheme](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/swaggerDoc.png "API error handling") +![Swagger API Scheme](../../assets/images/swaggerDoc.png "API error handling") diff --git a/sections/projectstructre/breakintcomponents.basque.md b/sections/projectstructre/breakintcomponents.basque.md index 1e2b02c01..82e02f595 100644 --- a/sections/projectstructre/breakintcomponents.basque.md +++ b/sections/projectstructre/breakintcomponents.basque.md @@ -26,10 +26,10 @@ Beraz, zer oihukatzen du zure aplikazioaren egiturak? Zure direktorioko egiturar ### Zuzena: antolatu zure proiektua aparteko osagaietan -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/structurebycomponents.PNG "Antolatu proiektua osagaietan") +![alt text](../../assets/images/structurebycomponents.PNG "Antolatu proiektua osagaietan")

### Okerra: taldekatu zure fitxategiak rol teknikoen arabera -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/structurebyroles.PNG "Antolatu proiektua rol teknikoen arabera") +![alt text](../../assets/images/structurebyroles.PNG "Antolatu proiektua rol teknikoen arabera") diff --git a/sections/projectstructre/breakintcomponents.brazilian-portuguese.md b/sections/projectstructre/breakintcomponents.brazilian-portuguese.md index 660b0be9d..f94491fda 100644 --- a/sections/projectstructre/breakintcomponents.brazilian-portuguese.md +++ b/sections/projectstructre/breakintcomponents.brazilian-portuguese.md @@ -27,10 +27,10 @@ Então, o que a arquitetura da sua aplicação grita? Quando você olha para a e ### Bom: estruture sua solução por componentes independentes -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/structurebycomponents.PNG "Solução de estruturação por componentes") +![alt text](../../assets/images/structurebycomponents.PNG "Solução de estruturação por componentes")

### Ruim: Agrupe seus arquivos por papel técnico -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/structurebyroles.PNG "Solução de estruturação por funções técnicas") +![alt text](../../assets/images/structurebyroles.PNG "Solução de estruturação por funções técnicas") diff --git a/sections/projectstructre/breakintcomponents.chinese.md b/sections/projectstructre/breakintcomponents.chinese.md index d4ae21dff..df143d8ac 100644 --- a/sections/projectstructre/breakintcomponents.chinese.md +++ b/sections/projectstructre/breakintcomponents.chinese.md @@ -27,10 +27,10 @@

### 推荐: 通过独立组件构建解决方案 -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/structurebycomponents.PNG "Structuring solution by components") +![alt text](../../assets/images/structurebycomponents.PNG "Structuring solution by components")

### 避免: 按技术角色对文件进行分组 -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/structurebyroles.PNG "Structuring solution by technical roles") +![alt text](../../assets/images/structurebyroles.PNG "Structuring solution by technical roles") diff --git a/sections/projectstructre/breakintcomponents.french.md b/sections/projectstructre/breakintcomponents.french.md index 77e6ab0cf..fa6fc1664 100644 --- a/sections/projectstructre/breakintcomponents.french.md +++ b/sections/projectstructre/breakintcomponents.french.md @@ -28,10 +28,10 @@ Alors, est-ce que est l'architecture de votre application parle d'elle-même ? Q ### Bon : Organisez votre solution avec des composants autonomes -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/structurebycomponents.PNG "Solution d'organisation par composants") +![alt text](../../assets/images/structurebycomponents.PNG "Solution d'organisation par composants")

### Mauvais : Regroupez vos fichiers selon leur rôle technique -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/structurebyroles.PNG "Solution d'organisation par rôles techniques") +![alt text](../../assets/images/structurebyroles.PNG "Solution d'organisation par rôles techniques") diff --git a/sections/projectstructre/breakintcomponents.japanese.md b/sections/projectstructre/breakintcomponents.japanese.md index 43615342e..1cdc8f341 100644 --- a/sections/projectstructre/breakintcomponents.japanese.md +++ b/sections/projectstructre/breakintcomponents.japanese.md @@ -28,10 +28,10 @@ ### 良い: 自己完結型のコンポーネントでソリューションを構築する -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/structurebycomponents.PNG "コンポーネントによるソリューションの構築") +![alt text](../../assets/images/structurebycomponents.PNG "コンポーネントによるソリューションの構築")

### 悪い: 技術的な役割ごとにファイルをグループ化 -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/structurebyroles.PNG "技術的な役割によるソリューションの構築") +![alt text](../../assets/images/structurebyroles.PNG "技術的な役割によるソリューションの構築") diff --git a/sections/projectstructre/breakintcomponents.korean.md b/sections/projectstructre/breakintcomponents.korean.md index a35f23509..1023f7109 100644 --- a/sections/projectstructre/breakintcomponents.korean.md +++ b/sections/projectstructre/breakintcomponents.korean.md @@ -28,10 +28,10 @@ MartinFowler.com 블로그로부터 ### 좋은예: 자족적인 컴포넌트 기반으로 설계하라 -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/structurebycomponents.PNG "Structuring solution by components") +![alt text](../../assets/images/structurebycomponents.PNG "Structuring solution by components")

### 나쁜예: 파일을 기술적인 역할별로 모아라 -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/structurebyroles.PNG "Structuring solution by technical roles") +![alt text](../../assets/images/structurebyroles.PNG "Structuring solution by technical roles") diff --git a/sections/projectstructre/breakintcomponents.md b/sections/projectstructre/breakintcomponents.md index 1e1bcf087..93f595f49 100644 --- a/sections/projectstructre/breakintcomponents.md +++ b/sections/projectstructre/breakintcomponents.md @@ -28,10 +28,10 @@ So what does the architecture of your application scream? When you look at the t ### Good: Structure your solution by self-contained components -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/structurebycomponents.PNG "Structuring solution by components") +![alt text](../../assets/images/structurebycomponents.PNG "Structuring solution by components")

### Bad: Group your files by technical role -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/structurebyroles.PNG "Structuring solution by technical roles") +![alt text](../../assets/images/structurebyroles.PNG "Structuring solution by technical roles") diff --git a/sections/projectstructre/breakintcomponents.polish.md b/sections/projectstructre/breakintcomponents.polish.md index 62098e97b..a91064d8d 100644 --- a/sections/projectstructre/breakintcomponents.polish.md +++ b/sections/projectstructre/breakintcomponents.polish.md @@ -27,10 +27,10 @@ Więc co krzyczy architektura twojej aplikacji? Gdy spojrzysz na strukturę kata ### Dobre: Skonstruuj swoje rozwiązanie według samodzielnych komponentów -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/structurebycomponents.PNG "Structuring solution by components") +![alt text](../../assets/images/structurebycomponents.PNG "Structuring solution by components")

### Złe: Pogrupuj pliki według roli technicznej -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/structurebyroles.PNG "Structuring solution by technical roles") +![alt text](../../assets/images/structurebyroles.PNG "Structuring solution by technical roles") diff --git a/sections/projectstructre/breakintcomponents.russian.md b/sections/projectstructre/breakintcomponents.russian.md index 7e5c36706..5830ba974 100644 --- a/sections/projectstructre/breakintcomponents.russian.md +++ b/sections/projectstructre/breakintcomponents.russian.md @@ -28,10 +28,10 @@ ### Хорошо: структурируйте свое решение по отдельным компонентам -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/structurebycomponents.PNG "Structuring solution by components") +![alt text](../../assets/images/structurebycomponents.PNG "Structuring solution by components")

### Плохо: сгруппируйте файлы по техническим ролям -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/structurebyroles.PNG "Structuring solution by technical roles") +![alt text](../../assets/images/structurebyroles.PNG "Structuring solution by technical roles") diff --git a/sections/projectstructre/createlayers.basque.md b/sections/projectstructre/createlayers.basque.md index c8f5aa631..6c13bc0ee 100644 --- a/sections/projectstructre/createlayers.basque.md +++ b/sections/projectstructre/createlayers.basque.md @@ -4,10 +4,10 @@ ### Osagaien kodea geruzatan banandu: web, zerbitzuak, eta Datuen Sarbide Geruza (DSG) (Ingelesez Data Access Layer, DAL) -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/structurebycomponents.PNG "Osagaien kodea geruzatan banandu") +![alt text](../../assets/images/structurebycomponents.PNG "Osagaien kodea geruzatan banandu")

### Minutu bateko azalpena: geruzak nahastearen eragozpena -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/keepexpressinweb.gif "Geruzak nahastearen eragozpena") +![alt text](../../assets/images/keepexpressinweb.gif "Geruzak nahastearen eragozpena") diff --git a/sections/projectstructre/createlayers.brazilian-portuguese.md b/sections/projectstructre/createlayers.brazilian-portuguese.md index 8990640f5..8d015ce45 100644 --- a/sections/projectstructre/createlayers.brazilian-portuguese.md +++ b/sections/projectstructre/createlayers.brazilian-portuguese.md @@ -4,10 +4,10 @@ ### Separe o código do componente em camadas: web, serviços e DAL -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/structurebycomponents.PNG "Separe o código do componente em camadas") +![alt text](../../assets/images/structurebycomponents.PNG "Separe o código do componente em camadas")

### Explicação em 1 minuto: A desvantagem de misturar camadas -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/keepexpressinweb.gif "A desvantagem de misturar camadas") +![alt text](../../assets/images/keepexpressinweb.gif "A desvantagem de misturar camadas") diff --git a/sections/projectstructre/createlayers.chinese.md b/sections/projectstructre/createlayers.chinese.md index 0ab1cc1e9..4d431f0f9 100644 --- a/sections/projectstructre/createlayers.chinese.md +++ b/sections/projectstructre/createlayers.chinese.md @@ -3,9 +3,9 @@

### 将组件代码分成web, services, DAL层 -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/structurebycomponents.PNG "Separate component code into layers") +![alt text](../../assets/images/structurebycomponents.PNG "Separate component code into layers")

### 1分钟说明：混合层的缺点 -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/keepexpressinweb.gif "The downside of mixing layers") +![alt text](../../assets/images/keepexpressinweb.gif "The downside of mixing layers") diff --git a/sections/projectstructre/createlayers.french.md b/sections/projectstructre/createlayers.french.md index f514e4405..a6d4d4d7e 100644 --- a/sections/projectstructre/createlayers.french.md +++ b/sections/projectstructre/createlayers.french.md @@ -4,10 +4,10 @@ ### Séparez le code des composants en strates : web, services et couche d'accès aux données (DAL) -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/structurebycomponents.PNG "Séparez le code des composants en strates") +![alt text](../../assets/images/structurebycomponents.PNG "Séparez le code des composants en strates")

### Explication en 1 min : l'inconvénient de mélanger les strates -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/keepexpressinweb.gif "L'inconvénient de mélanger les strates") +![alt text](../../assets/images/keepexpressinweb.gif "L'inconvénient de mélanger les strates") diff --git a/sections/projectstructre/createlayers.japanese.md b/sections/projectstructre/createlayers.japanese.md index e6c1356cf..dda7fb23c 100644 --- a/sections/projectstructre/createlayers.japanese.md +++ b/sections/projectstructre/createlayers.japanese.md @@ -4,10 +4,10 @@ ### コンポーネントコードをウェブ、サービス、DAL のレイヤーに分ける -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/structurebycomponents.PNG "コンポーネントコードを階層化する") +![alt text](../../assets/images/structurebycomponents.PNG "コンポーネントコードを階層化する")

### 1分解説: レイヤーを混ぜることのデメリット -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/keepexpressinweb.gif "レイヤーを混ぜることのデメリット") +![alt text](../../assets/images/keepexpressinweb.gif "レイヤーを混ぜることのデメリット") diff --git a/sections/projectstructre/createlayers.korean.md b/sections/projectstructre/createlayers.korean.md index c1d89a628..0278b8f20 100644 --- a/sections/projectstructre/createlayers.korean.md +++ b/sections/projectstructre/createlayers.korean.md @@ -4,10 +4,10 @@ ### 컴포넌트 코드를 웹, 서비스, 데이터 접근 언어(DAL) 계층으로 나누어라 -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/structurebycomponents.PNG "Separate component code into layers") +![alt text](../../assets/images/structurebycomponents.PNG "Separate component code into layers")

### 1분 설명: 계층을 섞으면 불리한 점 -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/keepexpressinweb.gif "The downside of mixing layers") +![alt text](../../assets/images/keepexpressinweb.gif "The downside of mixing layers") diff --git a/sections/projectstructre/createlayers.md b/sections/projectstructre/createlayers.md index 802452b28..bd02a1af0 100644 --- a/sections/projectstructre/createlayers.md +++ b/sections/projectstructre/createlayers.md @@ -4,10 +4,10 @@ ### Separate component code into layers: web, services, and Data Access Layer (DAL) -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/structurebycomponents.PNG "Separate component code into layers") +![alt text](../../assets/images/structurebycomponents.PNG "Separate component code into layers")

### 1 min explainer: The downside of mixing layers -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/keepexpressinweb.gif "The downside of mixing layers") +![alt text](../../assets/images/keepexpressinweb.gif "The downside of mixing layers") diff --git a/sections/projectstructre/createlayers.polish.md b/sections/projectstructre/createlayers.polish.md index 6c068cd8e..a9d30263c 100644 --- a/sections/projectstructre/createlayers.polish.md +++ b/sections/projectstructre/createlayers.polish.md @@ -4,10 +4,10 @@ ### Rozdziel kod komponentu na warstwy: sieć, usługi i DAL -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/structurebycomponents.PNG "Separate component code into layers") +![alt text](../../assets/images/structurebycomponents.PNG "Separate component code into layers")

### 1 minuta wyjaśniania: Minusem mieszanie warstw -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/keepexpressinweb.gif "The downside of mixing layers") +![alt text](../../assets/images/keepexpressinweb.gif "The downside of mixing layers") diff --git a/sections/projectstructre/createlayers.russian.md b/sections/projectstructre/createlayers.russian.md index 00d5e69ba..b7c2865b0 100644 --- a/sections/projectstructre/createlayers.russian.md +++ b/sections/projectstructre/createlayers.russian.md @@ -4,10 +4,10 @@ ### Разделить код компонента на слои: веб, сервисы и DAL -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/structurebycomponents.PNG "Separate component code into layers") +![alt text](../../assets/images/structurebycomponents.PNG "Separate component code into layers")

### 1 минутное объяснение: обратная сторона смешения слоев -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/keepexpressinweb.gif "The downside of mixing layers") +![alt text](../../assets/images/keepexpressinweb.gif "The downside of mixing layers") diff --git a/sections/projectstructre/thincomponents.chinese.md b/sections/projectstructre/thincomponents.chinese.md index 6fc193ed3..5b036ddb4 100644 --- a/sections/projectstructre/thincomponents.chinese.md +++ b/sections/projectstructre/thincomponents.chinese.md @@ -18,9 +18,9 @@

### 推荐: 通过自包含的组件来构造解决方案 -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/structurebycomponents.PNG "Structuring solution by components") +![alt text](../../assets/images/structurebycomponents.PNG "Structuring solution by components")

### 避免: 通过技术角色对文件进行分组 -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/structurebyroles.PNG "Structuring solution by technical roles") +![alt text](../../assets/images/structurebyroles.PNG "Structuring solution by technical roles") diff --git a/sections/projectstructre/thincomponents.french.md b/sections/projectstructre/thincomponents.french.md index eb3abde05..91c5e05c0 100644 --- a/sections/projectstructre/thincomponents.french.md +++ b/sections/projectstructre/thincomponents.french.md @@ -18,10 +18,10 @@ Pour les applications de taille moyenne et supérieure, les monolithes sont vrai ### Bon : Organisez votre solution avec des composants autonomes -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/structurebycomponents.PNG "Solution d'organisation par composants") +![alt text](../../assets/images/structurebycomponents.PNG "Solution d'organisation par composants")

### Mauvais : Regroupez vos fichiers selon leur rôle technique -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/structurebyroles.PNG "Solution d'organisation par rôles techniques") +![alt text](../../assets/images/structurebyroles.PNG "Solution d'organisation par rôles techniques") diff --git a/sections/projectstructre/thincomponents.japanese.md b/sections/projectstructre/thincomponents.japanese.md index 7d5535b6e..e586d6884 100644 --- a/sections/projectstructre/thincomponents.japanese.md +++ b/sections/projectstructre/thincomponents.japanese.md @@ -18,10 +18,10 @@ For medium sized apps and above, monoliths are really bad - one big software wit ### Good: Structure your solution by self-contained components -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/structurebycomponents.PNG "Structuring solution by components") +![alt text](../../assets/images/structurebycomponents.PNG "Structuring solution by components")

### Bad: Group your files by technical role -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/structurebyroles.PNG "Structuring solution by technical roles") +![alt text](../../assets/images/structurebyroles.PNG "Structuring solution by technical roles") diff --git a/sections/projectstructre/thincomponents.md b/sections/projectstructre/thincomponents.md index 7d5535b6e..e586d6884 100644 --- a/sections/projectstructre/thincomponents.md +++ b/sections/projectstructre/thincomponents.md @@ -18,10 +18,10 @@ For medium sized apps and above, monoliths are really bad - one big software wit ### Good: Structure your solution by self-contained components -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/structurebycomponents.PNG "Structuring solution by components") +![alt text](../../assets/images/structurebycomponents.PNG "Structuring solution by components")

### Bad: Group your files by technical role -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/structurebyroles.PNG "Structuring solution by technical roles") +![alt text](../../assets/images/structurebyroles.PNG "Structuring solution by technical roles") diff --git a/sections/projectstructre/thincomponents.russian.md b/sections/projectstructre/thincomponents.russian.md index 394f3dbe6..6f3c6a1be 100644 --- a/sections/projectstructre/thincomponents.russian.md +++ b/sections/projectstructre/thincomponents.russian.md @@ -18,10 +18,10 @@ ### Хорошо: структурируйте свое решение по отдельным компонентам -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/structurebycomponents.PNG "Structuring solution by components") +![alt text](../../assets/images/structurebycomponents.PNG "Structuring solution by components")

### Плохо: сгруппируйте файлы по техническим ролям -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/structurebyroles.PNG "Structuring solution by technical roles") +![alt text](../../assets/images/structurebyroles.PNG "Structuring solution by technical roles") diff --git a/sections/projectstructre/wraputilities.basque.md b/sections/projectstructre/wraputilities.basque.md index cb4d64067..18efeeb0f 100644 --- a/sections/projectstructre/wraputilities.basque.md +++ b/sections/projectstructre/wraputilities.basque.md @@ -12,4 +12,4 @@ Hazten hasi eta zerbitzari ezberdinetan antzeko baliabideak erabiltzen dituzten ### Partekatu zure baliabide propioak ingurune eta osagaietan -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/Privatenpm.png "Antolatu proiektua osagaietan") +![alt text](../../assets/images/Privatenpm.png "Antolatu proiektua osagaietan") diff --git a/sections/projectstructre/wraputilities.brazilian-portuguese.md b/sections/projectstructre/wraputilities.brazilian-portuguese.md index c054b4d04..13d54d763 100644 --- a/sections/projectstructre/wraputilities.brazilian-portuguese.md +++ b/sections/projectstructre/wraputilities.brazilian-portuguese.md @@ -10,4 +10,4 @@ Quando você começa a crescer e tem componentes diferentes em servidores difere ### Compartilhando seus próprios utilitários comuns em ambientes e componentes -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/Privatenpm.png "Solução de estruturação por componentes") +![alt text](../../assets/images/Privatenpm.png "Solução de estruturação por componentes") diff --git a/sections/projectstructre/wraputilities.chinese.md b/sections/projectstructre/wraputilities.chinese.md index 15511bf97..aa9e1a96b 100644 --- a/sections/projectstructre/wraputilities.chinese.md +++ b/sections/projectstructre/wraputilities.chinese.md @@ -11,4 +11,4 @@ ### 在环境和组件中共享你自己的公用实用工具 -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/Privatenpm.png "构建解决方案的组件") +![alt text](../../assets/images/Privatenpm.png "构建解决方案的组件") diff --git a/sections/projectstructre/wraputilities.french.md b/sections/projectstructre/wraputilities.french.md index 661d1b84a..523c5fc52 100644 --- a/sections/projectstructre/wraputilities.french.md +++ b/sections/projectstructre/wraputilities.french.md @@ -10,4 +10,4 @@ Une fois que vous commencez à vous développer et que vous avez différents com ### Partage de vos propres utilitaires communs entre les environnements et les composants -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/Privatenpm.png "Solution d'organisation par composants") +![alt text](../../assets/images/Privatenpm.png "Solution d'organisation par composants") diff --git a/sections/projectstructre/wraputilities.japanese.md b/sections/projectstructre/wraputilities.japanese.md index b9a703d05..52060026e 100644 --- a/sections/projectstructre/wraputilities.japanese.md +++ b/sections/projectstructre/wraputilities.japanese.md @@ -10,4 +10,4 @@ ### 環境やコンポーネント横断で独自の共通ユーティリティを共有する -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/Privatenpm.png "コンポーネントでソリューションを構築する") +![alt text](../../assets/images/Privatenpm.png "コンポーネントでソリューションを構築する") diff --git a/sections/projectstructre/wraputilities.korean.md b/sections/projectstructre/wraputilities.korean.md index 9265ea317..8bfaf69a8 100644 --- a/sections/projectstructre/wraputilities.korean.md +++ b/sections/projectstructre/wraputilities.korean.md @@ -10,4 +10,4 @@ ### 당신만의 공유 유틸리티들을 환경과 컴포넌츠에 공유하기 -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/Privatenpm.png "Structuring solution by components") +![alt text](../../assets/images/Privatenpm.png "Structuring solution by components") diff --git a/sections/projectstructre/wraputilities.md b/sections/projectstructre/wraputilities.md index ed3639007..4d9e3da62 100644 --- a/sections/projectstructre/wraputilities.md +++ b/sections/projectstructre/wraputilities.md @@ -10,4 +10,4 @@ Once you start growing and have different components on different servers which ### Sharing your own common utilities across environments and components -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/Privatenpm.png "Structuring solution by components") +![alt text](../../assets/images/Privatenpm.png "Structuring solution by components") diff --git a/sections/projectstructre/wraputilities.polish.md b/sections/projectstructre/wraputilities.polish.md index e823509de..bbd4432a1 100644 --- a/sections/projectstructre/wraputilities.polish.md +++ b/sections/projectstructre/wraputilities.polish.md @@ -10,4 +10,4 @@ Kiedy zaczniesz się rozwijać i będziesz mieć różne komponenty na różnych ### Udostępnianie własnych wspólnych narzędzi w różnych środowiskach i komponentach -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/Privatenpm.png "Structuring solution by components") +![alt text](../../assets/images/Privatenpm.png "Structuring solution by components") diff --git a/sections/projectstructre/wraputilities.russian.md b/sections/projectstructre/wraputilities.russian.md index 02a1fac70..3520ef383 100644 --- a/sections/projectstructre/wraputilities.russian.md +++ b/sections/projectstructre/wraputilities.russian.md @@ -10,4 +10,4 @@ ### Совместное использование собственных общих утилит в средах и компонентах -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/Privatenpm.png "Structuring solution by components") +![alt text](../../assets/images/Privatenpm.png "Structuring solution by components") diff --git a/sections/template.basque.md b/sections/template.basque.md index 0c3fb0375..684837ecc 100644 --- a/sections/template.basque.md +++ b/sections/template.basque.md @@ -34,14 +34,14 @@ Blogean, pouchdb.comek “Node Promesak hitz gakoarentzat 11.posizioa du ### Adibidea: CodeClimaterekin funtzio konplexuen analisia (iragarkia) -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/codeanalysis-climate-complex-methods.PNG "Funtzio konplexuen analisia") +![alt text](../assets/images/codeanalysis-climate-complex-methods.PNG "Funtzio konplexuen analisia") ### Adibidea: CodeClimaterekin kode analisi joerak eta historia (iragarkia) -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/codeanalysis-climate-history.PNG "Kode analisiaren historia") +![alt text](../assets/images/codeanalysis-climate-history.PNG "Kode analisiaren historia") ### Adibidea: SonarQuberekin kode analisiaren laburpena eta joerak (iragarkia) -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/codeanalysis-sonarqube-dashboard.PNG "Kode analisiaren historia") +![alt text](../assets/images/codeanalysis-sonarqube-dashboard.PNG "Kode analisiaren historia")

diff --git a/sections/template.md b/sections/template.md index d4c154f29..9ff2cc381 100644 --- a/sections/template.md +++ b/sections/template.md @@ -34,15 +34,15 @@ code here ### Example: Complex methods analysis with CodeClimate (commercial) -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/codeanalysis-climate-complex-methods.PNG "Complex methods analysis") +![alt text](../assets/images/codeanalysis-climate-complex-methods.PNG "Complex methods analysis") ### Example: Code analysis trends and history with CodeClimate (commercial) -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/codeanalysis-climate-history.PNG "Code analysis history") +![alt text](../assets/images/codeanalysis-climate-history.PNG "Code analysis history") ### Example: Code analysis summary and trends with SonarQube (commercial) -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/codeanalysis-sonarqube-dashboard.PNG "Code analysis history") +![alt text](../assets/images/codeanalysis-sonarqube-dashboard.PNG "Code analysis history")

diff --git a/sections/testingandquality/3-parts-in-name.basque.md b/sections/testingandquality/3-parts-in-name.basque.md index 61d030ea9..0fc762eb0 100644 --- a/sections/testingandquality/3-parts-in-name.basque.md +++ b/sections/testingandquality/3-parts-in-name.basque.md @@ -50,6 +50,6 @@ describe('Produktu Zerbitzua', () => { ["30 Node.jsren proba jarraibide egokiak" blogetik hartua, Yoni Goldbergen eskutik](https://medium.com/@me_37286/yoni-goldberg-javascript-nodejs-testing-best-practices-2b98924c9347) -![Proba txostenaren adibidea](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/test-report-like-requirements.jpeg "Proba txostenaren adibidea") +![Proba txostenaren adibidea](../../assets/images/test-report-like-requirements.jpeg "Proba txostenaren adibidea")

diff --git a/sections/testingandquality/3-parts-in-name.brazilian-portuguese.md b/sections/testingandquality/3-parts-in-name.brazilian-portuguese.md index 97ddc0479..497dc6dfd 100644 --- a/sections/testingandquality/3-parts-in-name.brazilian-portuguese.md +++ b/sections/testingandquality/3-parts-in-name.brazilian-portuguese.md @@ -49,6 +49,6 @@ describe('Serviço de Produtos', function() { [Do blog "30 Node.js testing best practices" por Yoni Goldberg](https://medium.com/@me_37286/yoni-goldberg-javascript-nodejs-testing-best-practices-2b98924c9347) - ![Um exemplo de relatório de teste](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/test-report-like-requirements.jpeg "Um exemplo de relatório de teste") + ![Um exemplo de relatório de teste](../../assets/images/test-report-like-requirements.jpeg "Um exemplo de relatório de teste") -

\ No newline at end of file +

diff --git a/sections/testingandquality/3-parts-in-name.french.md b/sections/testingandquality/3-parts-in-name.french.md index b3365a54a..083dd76eb 100644 --- a/sections/testingandquality/3-parts-in-name.french.md +++ b/sections/testingandquality/3-parts-in-name.french.md @@ -49,6 +49,6 @@ describe('Service Produits', () => { [Extrait du blog de « 30 bonnes pratiques de test avec Node.js » par Yoni Goldberg](https://medium.com/@me_37286/yoni-goldberg-javascript-nodejs-testing-best-practices-2b98924c9347) - ![Un exemple de rapport de test](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/test-report-like-requirements.jpeg "Un exemple de rapport de test") + ![Un exemple de rapport de test](../../assets/images/test-report-like-requirements.jpeg "Un exemple de rapport de test") -

\ No newline at end of file +

diff --git a/sections/testingandquality/3-parts-in-name.japanese.md b/sections/testingandquality/3-parts-in-name.japanese.md index 4227662e3..4766a57f8 100644 --- a/sections/testingandquality/3-parts-in-name.japanese.md +++ b/sections/testingandquality/3-parts-in-name.japanese.md @@ -49,6 +49,6 @@ describe('Products Service', () => { [Yoni Goldberg によるブログ記事 "30 Node.js testing best practices"](https://medium.com/@me_37286/yoni-goldberg-javascript-nodejs-testing-best-practices-2b98924c9347) - ![テストレポートの例](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/test-report-like-requirements.jpeg "テストレポートの例") + ![テストレポートの例](../../assets/images/test-report-like-requirements.jpeg "テストレポートの例") -

\ No newline at end of file +

diff --git a/sections/testingandquality/3-parts-in-name.md b/sections/testingandquality/3-parts-in-name.md index 0568937c5..2964e929b 100644 --- a/sections/testingandquality/3-parts-in-name.md +++ b/sections/testingandquality/3-parts-in-name.md @@ -49,6 +49,6 @@ describe('Products Service', () => { [From the blog "30 Node.js testing best practices" by Yoni Goldberg](https://medium.com/@me_37286/yoni-goldberg-javascript-nodejs-testing-best-practices-2b98924c9347) - ![A test report example](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/test-report-like-requirements.jpeg "A test report example") + ![A test report example](../../assets/images/test-report-like-requirements.jpeg "A test report example")

diff --git a/sections/testingandquality/3-parts-in-name.polish.md b/sections/testingandquality/3-parts-in-name.polish.md index ca6beff51..1f2821c1d 100644 --- a/sections/testingandquality/3-parts-in-name.polish.md +++ b/sections/testingandquality/3-parts-in-name.polish.md @@ -49,6 +49,6 @@ describe('Products Service', () => { [Z bloga "30 Node.js testing best practices" od Yoni Goldberg](https://medium.com/@me_37286/yoni-goldberg-javascript-nodejs-testing-best-practices-2b98924c9347) - ![Przykład raportu testu](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/test-report-like-requirements.jpeg "A test report example") + ![Przykład raportu testu](../../assets/images/test-report-like-requirements.jpeg "A test report example")

diff --git a/sections/testingandquality/3-parts-in-name.russian.md b/sections/testingandquality/3-parts-in-name.russian.md index 17c4131c0..ddf7f9ace 100644 --- a/sections/testingandquality/3-parts-in-name.russian.md +++ b/sections/testingandquality/3-parts-in-name.russian.md @@ -49,6 +49,6 @@ describe('Products Service', () => { [From the blog "30 Node.js testing best practices" by Yoni Goldberg](https://medium.com/@me_37286/yoni-goldberg-javascript-nodejs-testing-best-practices-2b98924c9347) - ![A test report example](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/test-report-like-requirements.jpeg "A test report example") + ![A test report example](../../assets/images/test-report-like-requirements.jpeg "A test report example") -

\ No newline at end of file +

diff --git a/sections/testingandquality/bumpversion.japanese.md b/sections/testingandquality/bumpversion.japanese.md index 56e66ff1d..8e5714058 100644 --- a/sections/testingandquality/bumpversion.japanese.md +++ b/sections/testingandquality/bumpversion.japanese.md @@ -24,4 +24,4 @@ code here ### Image title -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/swaggerDoc.png "API error handling") +![alt text](../../assets/images/swaggerDoc.png "API error handling") diff --git a/sections/testingandquality/bumpversion.md b/sections/testingandquality/bumpversion.md index 56e66ff1d..8e5714058 100644 --- a/sections/testingandquality/bumpversion.md +++ b/sections/testingandquality/bumpversion.md @@ -24,4 +24,4 @@ code here ### Image title -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/swaggerDoc.png "API error handling") +![alt text](../../assets/images/swaggerDoc.png "API error handling") diff --git a/sections/testingandquality/citools.basque.md b/sections/testingandquality/citools.basque.md index 29fe6cdc7..78059d822 100644 --- a/sections/testingandquality/citools.basque.md +++ b/sections/testingandquality/citools.basque.md @@ -42,10 +42,10 @@ jobs: ### Circle CI: ia zero prestakuntzadun hodeieko IEa -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/circleci.png "API erroreen kudeaketa") +![alt text](../../assets/images/circleci.png "API erroreen kudeaketa") ### Jenkins: IE sofistikatu eta sendoa -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/jenkins_dashboard.png "API erroreen kudeaketa") +![alt text](../../assets/images/jenkins_dashboard.png "API erroreen kudeaketa")

diff --git a/sections/testingandquality/citools.brazilian-portuguese.md b/sections/testingandquality/citools.brazilian-portuguese.md index 741a5cb80..fff68be52 100644 --- a/sections/testingandquality/citools.brazilian-portuguese.md +++ b/sections/testingandquality/citools.brazilian-portuguese.md @@ -42,10 +42,10 @@ jobs: ### Circle CI - CI com quase zero configuração em nuvem -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/circleci.png "manipulador de erros do API") +![alt text](../../assets/images/circleci.png "manipulador de erros do API") ### Jenkins - CI sofisticado e robusto -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/jenkins_dashboard.png "manipulador de erros do API") +![alt text](../../assets/images/jenkins_dashboard.png "manipulador de erros do API")

diff --git a/sections/testingandquality/citools.chinese.md b/sections/testingandquality/citools.chinese.md index 21495796d..0817c59b6 100644 --- a/sections/testingandquality/citools.chinese.md +++ b/sections/testingandquality/citools.chinese.md @@ -44,10 +44,10 @@ jobs: ### Circle CI - 几乎零设置的云CI -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/circleci.png "API error handling") +![alt text](../../assets/images/circleci.png "API error handling") ### Jenkins - 完善和强大的CI -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/jenkins_dashboard.png "API error handling") +![alt text](../../assets/images/jenkins_dashboard.png "API error handling")

diff --git a/sections/testingandquality/citools.french.md b/sections/testingandquality/citools.french.md index 9e27ea763..8b33bc1d7 100644 --- a/sections/testingandquality/citools.french.md +++ b/sections/testingandquality/citools.french.md @@ -42,10 +42,10 @@ jobs: ### Circle CI - CI du cloud avec une configuration presque nul -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/circleci.png "Gestion des erreurs API") +![alt text](../../assets/images/circleci.png "Gestion des erreurs API") ### Jenkins - CI sophistiqué et robuste -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/jenkins_dashboard.png "Gestion des erreurs API") +![alt text](../../assets/images/jenkins_dashboard.png "Gestion des erreurs API")

diff --git a/sections/testingandquality/citools.japanese.md b/sections/testingandquality/citools.japanese.md index 3b1d22120..787cfa333 100644 --- a/sections/testingandquality/citools.japanese.md +++ b/sections/testingandquality/citools.japanese.md @@ -42,10 +42,10 @@ jobs: ### Circle CI - ほぼ設定の必要ないクラウド CI -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/circleci.png "Circle CI") +![alt text](../../assets/images/circleci.png "Circle CI") ### Jenkins - 洗練された、堅牢な CI -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/jenkins_dashboard.png "Jenkins") +![alt text](../../assets/images/jenkins_dashboard.png "Jenkins")

diff --git a/sections/testingandquality/citools.korean.md b/sections/testingandquality/citools.korean.md index 96eb69110..e13b7279c 100644 --- a/sections/testingandquality/citools.korean.md +++ b/sections/testingandquality/citools.korean.md @@ -42,10 +42,10 @@ jobs: ### Circle CI - almost zero setup cloud CI -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/circleci.png "API error handling") +![alt text](../../assets/images/circleci.png "API error handling") ### Jenkins - sophisticated and robust CI -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/jenkins_dashboard.png "API error handling") +![alt text](../../assets/images/jenkins_dashboard.png "API error handling")

diff --git a/sections/testingandquality/citools.md b/sections/testingandquality/citools.md index 16c6c16ae..375e89fea 100644 --- a/sections/testingandquality/citools.md +++ b/sections/testingandquality/citools.md @@ -42,10 +42,10 @@ jobs: ### Circle CI - almost zero setup cloud CI -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/circleci.png "API error handling") +![alt text](../../assets/images/circleci.png "API error handling") ### Jenkins - sophisticated and robust CI -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/jenkins_dashboard.png "API error handling") +![alt text](../../assets/images/jenkins_dashboard.png "API error handling")

diff --git a/sections/testingandquality/citools.polish.md b/sections/testingandquality/citools.polish.md index ae98f0a69..060bdd561 100644 --- a/sections/testingandquality/citools.polish.md +++ b/sections/testingandquality/citools.polish.md @@ -42,10 +42,10 @@ jobs: ### Circle CI - prawie zerowa konfiguracja CI w chmurze -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/circleci.png "API error handling") +![alt text](../../assets/images/circleci.png "API error handling") ### Jenkins - wyrafinowany i solidny CI -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/jenkins_dashboard.png "API error handling") +![alt text](../../assets/images/jenkins_dashboard.png "API error handling")

diff --git a/sections/testingandquality/citools.russian.md b/sections/testingandquality/citools.russian.md index f46905269..e3c69b509 100644 --- a/sections/testingandquality/citools.russian.md +++ b/sections/testingandquality/citools.russian.md @@ -42,10 +42,10 @@ jobs: ### Circle CI - почти нулевая настройка облака CI -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/circleci.png "API error handling") +![alt text](../../assets/images/circleci.png "API error handling") ### Дженкинс - сложный и надежный CI -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/jenkins_dashboard.png "API error handling") +![alt text](../../assets/images/jenkins_dashboard.png "API error handling")

diff --git a/sections/testingandquality/refactoring.basque.md b/sections/testingandquality/refactoring.basque.md index 0b58748b6..3ec63c028 100644 --- a/sections/testingandquality/refactoring.basque.md +++ b/sections/testingandquality/refactoring.basque.md @@ -29,15 +29,15 @@ Tresna horiek zure IE eraikuntzari gehitzeak kalitatea egiaztatzeko prozesua aut ### Adibidea: Funtzio konplexuen analisia CodeClimaterekin (komertziala) -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/codeanalysis-climate-complex-methods.PNG "Funtzio konplexuen analisia") +![alt text](../../assets/images/codeanalysis-climate-complex-methods.PNG "Funtzio konplexuen analisia") ### Adibidea: Kode analisiaren joerak eta CodeClimaterekin historia (komertziala) -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/codeanalysis-climate-history.PNG "Kode analisiaren historia") +![alt text](../../assets/images/codeanalysis-climate-history.PNG "Kode analisiaren historia") ### Adibidea: Kode analisiaren laburpena eta SonarQuberekin joerak (komertziala) -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/codeanalysis-sonarqube-dashboard.PNG "Kode analisiaren historia") +![alt text](../../assets/images/codeanalysis-sonarqube-dashboard.PNG "Kode analisiaren historia")

diff --git a/sections/testingandquality/refactoring.brazilian-portuguese.md b/sections/testingandquality/refactoring.brazilian-portuguese.md index 490266eda..52e2836f5 100644 --- a/sections/testingandquality/refactoring.brazilian-portuguese.md +++ b/sections/testingandquality/refactoring.brazilian-portuguese.md @@ -27,15 +27,15 @@ A refatoração é um processo importante no fluxo de desenvolvimento iterativo. ### Exemplo: Análise de métodos complexos com CodeClimate (comercial) -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/codeanalysis-climate-complex-methods.PNG "Análise de métodos complexos") +![alt text](../../assets/images/codeanalysis-climate-complex-methods.PNG "Análise de métodos complexos") ### Exemplo: tendências de análise de código e histórico com CodeClimate (comercial) -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/codeanalysis-climate-history.PNG "Histórico de análise de código") +![alt text](../../assets/images/codeanalysis-climate-history.PNG "Histórico de análise de código") ### Exemplo: Resumo de análise de código e tendências com o SonarQube (comercial) -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/codeanalysis-sonarqube-dashboard.PNG "Histórico de análise de código") +![alt text](../../assets/images/codeanalysis-sonarqube-dashboard.PNG "Histórico de análise de código")

diff --git a/sections/testingandquality/refactoring.french.md b/sections/testingandquality/refactoring.french.md index 985d39741..6bd7f37db 100644 --- a/sections/testingandquality/refactoring.french.md +++ b/sections/testingandquality/refactoring.french.md @@ -29,15 +29,15 @@ seront toujours un problème si la qualité implicite de votre JavaScript est ma ### Exemple : analyse de méthodes complexes avec CodeClimate (commercial) -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/codeanalysis-climate-complex-methods.PNG "Analyse de méthodes complexes") +![alt text](../../assets/images/codeanalysis-climate-complex-methods.PNG "Analyse de méthodes complexes") ### Exemple : tendances et historique de l'analyse de code avec CodeClimate (commercial) -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/codeanalysis-climate-history.PNG "Historique d'analyse de code") +![alt text](../../assets/images/codeanalysis-climate-history.PNG "Historique d'analyse de code") ### Exemple : résumé et tendances de l'analyse de code avec SonarQube (commercial) -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/codeanalysis-sonarqube-dashboard.PNG "Historique d'analyse de code") +![alt text](../../assets/images/codeanalysis-sonarqube-dashboard.PNG "Historique d'analyse de code")

diff --git a/sections/testingandquality/refactoring.japanese.md b/sections/testingandquality/refactoring.japanese.md index 3bb026fdb..0ee0d0702 100644 --- a/sections/testingandquality/refactoring.japanese.md +++ b/sections/testingandquality/refactoring.japanese.md @@ -27,15 +27,15 @@ ### 例: CodeClimate を使用した複雑なメソッドの解析（商用） -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/codeanalysis-climate-complex-methods.PNG "複雑なメソッドの解析") +![alt text](../../assets/images/codeanalysis-climate-complex-methods.PNG "複雑なメソッドの解析") ### 例: CodeClimate を使用したコード解析結果の傾向と履歴（商用） -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/codeanalysis-climate-history.PNG "コード解析の履歴") +![alt text](../../assets/images/codeanalysis-climate-history.PNG "コード解析の履歴") ### 例: コード解析結果のサマリーと傾向（商用） -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/codeanalysis-sonarqube-dashboard.PNG "コード解析結果のサマリーと傾向") +![alt text](../../assets/images/codeanalysis-sonarqube-dashboard.PNG "コード解析結果のサマリーと傾向")

diff --git a/sections/testingandquality/refactoring.md b/sections/testingandquality/refactoring.md index 99a506edc..804f9147b 100644 --- a/sections/testingandquality/refactoring.md +++ b/sections/testingandquality/refactoring.md @@ -29,15 +29,15 @@ will always be an issue if the underlying quality of your JavaScript is poor. ### Example: Complex methods analysis with CodeClimate (commercial) -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/codeanalysis-climate-complex-methods.PNG "Complex methods analysis") +![alt text](../../assets/images/codeanalysis-climate-complex-methods.PNG "Complex methods analysis") ### Example: Code analysis trends and history with CodeClimate (commercial) -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/codeanalysis-climate-history.PNG "Code analysis history") +![alt text](../../assets/images/codeanalysis-climate-history.PNG "Code analysis history") ### Example: Code analysis summary and trends with SonarQube (commercial) -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/codeanalysis-sonarqube-dashboard.PNG "Code analysis history") +![alt text](../../assets/images/codeanalysis-sonarqube-dashboard.PNG "Code analysis history")

diff --git a/sections/testingandquality/refactoring.polish.md b/sections/testingandquality/refactoring.polish.md index 6e2fce6f6..9af9e89dd 100644 --- a/sections/testingandquality/refactoring.polish.md +++ b/sections/testingandquality/refactoring.polish.md @@ -29,15 +29,15 @@ will always be an issue if the underlying quality of your JavaScript is poor. ### Przykład: Analiza złożonych metod za pomocą CodeClimate (komercyjna) -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/codeanalysis-climate-complex-methods.PNG "Complex methods analysis") +![alt text](../../assets/images/codeanalysis-climate-complex-methods.PNG "Complex methods analysis") ### Przykład: trendy i historia analizy kodu za pomocą CodeClimate (komercyjna) -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/codeanalysis-climate-history.PNG "Code analysis history") +![alt text](../../assets/images/codeanalysis-climate-history.PNG "Code analysis history") ### Przykład: Podsumowanie analizy kodu i trendy w SonarQube (komercyjna) -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/codeanalysis-sonarqube-dashboard.PNG "Code analysis history") +![alt text](../../assets/images/codeanalysis-sonarqube-dashboard.PNG "Code analysis history")

diff --git a/sections/testingandquality/refactoring.russian.md b/sections/testingandquality/refactoring.russian.md index 5693544c9..8a05fc8db 100644 --- a/sections/testingandquality/refactoring.russian.md +++ b/sections/testingandquality/refactoring.russian.md @@ -29,15 +29,15 @@ ### Пример: Анализ сложных методов с помощью CodeClimate (коммерческий) -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/codeanalysis-climate-complex-methods.PNG "Complex methods analysis") +![alt text](../../assets/images/codeanalysis-climate-complex-methods.PNG "Complex methods analysis") ### Пример: Тенденции и история анализа кода с CodeClimate (коммерческий) -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/codeanalysis-climate-history.PNG "Code analysis history") +![alt text](../../assets/images/codeanalysis-climate-history.PNG "Code analysis history") ### Пример: Сводка анализа кода и тенденции с SonarQube (коммерческий) -![alt text](https://github.com/goldbergyoni/nodebestpractices/blob/master/assets/images/codeanalysis-sonarqube-dashboard.PNG "Code analysis history") +![alt text](../../assets/images/codeanalysis-sonarqube-dashboard.PNG "Code analysis history")