From 49edbc42e3d23ccdf6a1653ced24740c8a66e9d3 Mon Sep 17 00:00:00 2001 From: Blind4Basics <32236948+Blind4Basics@users.noreply.github.com> Date: Mon, 13 Jul 2020 18:53:57 +0200 Subject: [PATCH 01/12] Update glossary.yml --- data/glossary.yml | 17 +++++++++++++++-- 1 file changed, 15 insertions(+), 2 deletions(-) diff --git a/data/glossary.yml b/data/glossary.yml index 181403ff..ff64ca89 100644 --- a/data/glossary.yml +++ b/data/glossary.yml @@ -39,7 +39,7 @@ - term: Allies description: Users who are following each others, or who are part of the same clan. - + - term: Approve (a kata, a translation) description: | Action to push a kata out of the beta process, giving it a rank (kyus). This can be done by power users. @@ -55,6 +55,19 @@ - term: Beta (kata/process) description: The beta process is the phase where a kata is visible to any other user in the database/[katas search page](https://www.codewars.com/kata/my-languages) but does not have a rank yet. It is to be tested by other users, so that it can be enhanced, modified, ranked and finally approved... or retired if not qualitative enough. +- term: Clan(s) + description: | + You can write the name of your clan/company/organisation through your `profile/account settings`. All the member of this clan are automatically recognized as allies of yours, hence are added to your personnal leaderboard in the [dashboard](#dashboard). + +- term: Collections(s) + description: | + Collections are sets/libraries of katas that any user can create, for any purpose. All collections are public. + links: + - title: Collections created by one user + url: https://www.codewars.com/users/Blind4Basics/authored_collections + - title: Browse through all collections + url: https://www.codewars.com/collections + - term: Contributor(s) description: User(s) who have either authored, approved, translated or modified a kata in any way (a list of them can be seen in the "Details" page of any kata. @@ -64,7 +77,7 @@ - title: Dan (rank) - Wikipedia url: https://en.wikipedia.org/wiki/Dan_(rank) -- term: Dashboard +- term: Dashboard description: This is the main page for a code warrior. You land there by clicking on the picture in the top left vertical bar (Codewars' logo). It contains kata suggestions, a leaderboard of you and your allies and a flow of the last comments posted anywhere on Codewars. links: - title: Codewars Dashboard From e886d538a6fdf14162b974b18beaee09b12fc0a0 Mon Sep 17 00:00:00 2001 From: Blind4Basics Date: Mon, 13 Jul 2020 16:56:10 +0000 Subject: [PATCH 02/12] Prettier --- data/glossary.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/data/glossary.yml b/data/glossary.yml index ff64ca89..1093e814 100644 --- a/data/glossary.yml +++ b/data/glossary.yml @@ -39,7 +39,7 @@ - term: Allies description: Users who are following each others, or who are part of the same clan. - + - term: Approve (a kata, a translation) description: | Action to push a kata out of the beta process, giving it a rank (kyus). This can be done by power users. @@ -67,7 +67,7 @@ url: https://www.codewars.com/users/Blind4Basics/authored_collections - title: Browse through all collections url: https://www.codewars.com/collections - + - term: Contributor(s) description: User(s) who have either authored, approved, translated or modified a kata in any way (a list of them can be seen in the "Details" page of any kata. From f39ef88b4ac28c61a448f3775c46536498a302c5 Mon Sep 17 00:00:00 2001 From: Blind4Basics <32236948+Blind4Basics@users.noreply.github.com> Date: Mon, 13 Jul 2020 19:06:11 +0200 Subject: [PATCH 03/12] Update glossary.yml --- data/glossary.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/data/glossary.yml b/data/glossary.yml index 1093e814..ed507e1d 100644 --- a/data/glossary.yml +++ b/data/glossary.yml @@ -57,7 +57,10 @@ - term: Clan(s) description: | - You can write the name of your clan/company/organisation through your `profile/account settings`. All the member of this clan are automatically recognized as allies of yours, hence are added to your personnal leaderboard in the [dashboard](#dashboard). + You can write the name of your clan/company/organisation through your `profile/account settings`. All the member of this clan are automatically recognized as allies of yours, hence are added to your personnal leaderboard in the dashboard. + links: + - title: Dashboard leaderboard + url: https://www.codewars.com/dashboard - term: Collections(s) description: | @@ -77,7 +80,7 @@ - title: Dan (rank) - Wikipedia url: https://en.wikipedia.org/wiki/Dan_(rank) -- term: Dashboard +- term: Dashboard description: This is the main page for a code warrior. You land there by clicking on the picture in the top left vertical bar (Codewars' logo). It contains kata suggestions, a leaderboard of you and your allies and a flow of the last comments posted anywhere on Codewars. links: - title: Codewars Dashboard From 494c63c29625a529ad81f10ce51853a198af5d75 Mon Sep 17 00:00:00 2001 From: Blind4Basics <32236948+Blind4Basics@users.noreply.github.com> Date: Mon, 13 Jul 2020 19:50:04 +0200 Subject: [PATCH 04/12] Update glossary.yml --- data/glossary.yml | 55 +++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 55 insertions(+) diff --git a/data/glossary.yml b/data/glossary.yml index ed507e1d..cb2785c5 100644 --- a/data/glossary.yml +++ b/data/glossary.yml @@ -119,6 +119,15 @@ * you enter the edit panel (_warning_: power users may have the possibility to enter the edit panel of some katas. If you do so before you solved it, you actually forfeit it). Forfeiting a kata makes you lose the opportunity to gain honor points or progress by completing this kata. +- term: Fork + description: | + In the solutions page of a kata, you can see the solutions of other users, and you can `fork` them to suggest modifications/enhancements. + Using the fork panel is the right way to try out a solution of another user, rather than copy it in the trainer of the kata. + +- term: Honor (points) + description: | + Honor points are those that are showing up in the top right corner of any codewars page. You can win honor points in different ways (completing katas, up votes on your comments or solutions, translations, creating katas, ...) + - term: Inactive (author) description: | Author of a kata who hasn't been connected for more than 30 days. When an author is inactive, some actions he's normally the only person allowed to do are doable by other people (power users with the required privilegees). @@ -154,6 +163,52 @@ - title: Kyū - Wikipedia url: https://en.wikipedia.org/wiki/Ky%C5%AB +- term: Language versions + description: | + A kata may be available in one or more languages (javascript, python, coq, ...), and for each language, there may be different language versions. Like, Node 8 or Node 10 for JS, or python 3.4.3 or 3.6 for python... + You can choose the language _and_ the language version in the trainer of a kata (amongst the available ones). + +- term: Leaderboards + description: | + Leaderboards are grouping different users according to different criteria. + links: + - title: Overall top 500 + url: https://www.codewars.com/users/leaderboard + - title: Top 500 by completed Katas + url: https://www.codewars.com/users/leaderboard/kata + - title: Top 500 by authored Katas & translations + url: https://www.codewars.com/users/leaderboard/authored + - title: Your "personnal" leaderboard (with your allies, in the dashboard) + url: https://www.codewars.com/dashboard + +- term: Markdowns (formatting) + description: | + CodeWars is responsive to `markdowns`. They allow you to format code or descriptions so that thay are properly readable for other users. + links: + - title: TODO + url: TODO + +- term: Merge conflicts + description: | + When a translation of a kata is published but some changes or done to the description (through the edit panel) before the translation gets approved, it becomes impossible to approve it because of those "merge conflicts". + To resolve this problem, you have to fork the translation and update the description starting with its current (new) version. + +- term: Mutation of the input + description: | + To keep it short...: ___Don't mutate the input... Ever___ (eg. don't use sort/append/push/remove/... and alike before doing a copy of the input). + This is about side effects, modifying the arguments (typically lists/arrays, or even strings if they are mutable in your language) sent to your function during the executions. This can have werid consequences, depending on how the tests are written. + Nowadays, most test suites are written in a way to avoid this kind of problem but typically, if you end up passing the fixed tests but failing all the random tests with something along the line of `[your result] should equal []`, you're most likely facing a "mutation of the input" problem. + Hence... Don't mutate the input. + +- term: Preloaded (code/section) + description: | + In a Kata, the preloaded section is code that is executed _before_ the solution of the user. The code hold by this section isn't visible, but every function or variable defined there is accessible through the code. + If you need/want to see the preloaded section of a Kata, open a fork of a solution _after_ you solved it. + +- term: Progress + description: | + Aside of honor points, you gain "progress" by completing Katas (and only that way). Progess is what is conditionning your current rank as a warrior. + - term: Publishing (kata) description: When you hit "publish" in the edit panel of a kata you created, it enters the beta process and becomes visible to anyone in the [katas search page](https://www.codewars.com/kata/my-languages). The beta process begins at the moment a kata is published. From 93cef78ec35c7af0785ada38feb3708e10810548 Mon Sep 17 00:00:00 2001 From: Blind4Basics Date: Mon, 13 Jul 2020 17:50:42 +0000 Subject: [PATCH 05/12] Prettier --- data/glossary.yml | 50 +++++++++++++++++++++++------------------------ 1 file changed, 25 insertions(+), 25 deletions(-) diff --git a/data/glossary.yml b/data/glossary.yml index cb2785c5..4b3b8a46 100644 --- a/data/glossary.yml +++ b/data/glossary.yml @@ -121,13 +121,13 @@ - term: Fork description: | - In the solutions page of a kata, you can see the solutions of other users, and you can `fork` them to suggest modifications/enhancements. - Using the fork panel is the right way to try out a solution of another user, rather than copy it in the trainer of the kata. - + In the solutions page of a kata, you can see the solutions of other users, and you can `fork` them to suggest modifications/enhancements. + Using the fork panel is the right way to try out a solution of another user, rather than copy it in the trainer of the kata. + - term: Honor (points) description: | - Honor points are those that are showing up in the top right corner of any codewars page. You can win honor points in different ways (completing katas, up votes on your comments or solutions, translations, creating katas, ...) - + Honor points are those that are showing up in the top right corner of any codewars page. You can win honor points in different ways (completing katas, up votes on your comments or solutions, translations, creating katas, ...) + - term: Inactive (author) description: | Author of a kata who hasn't been connected for more than 30 days. When an author is inactive, some actions he's normally the only person allowed to do are doable by other people (power users with the required privilegees). @@ -165,12 +165,12 @@ - term: Language versions description: | - A kata may be available in one or more languages (javascript, python, coq, ...), and for each language, there may be different language versions. Like, Node 8 or Node 10 for JS, or python 3.4.3 or 3.6 for python... - You can choose the language _and_ the language version in the trainer of a kata (amongst the available ones). - + A kata may be available in one or more languages (javascript, python, coq, ...), and for each language, there may be different language versions. Like, Node 8 or Node 10 for JS, or python 3.4.3 or 3.6 for python... + You can choose the language _and_ the language version in the trainer of a kata (amongst the available ones). + - term: Leaderboards description: | - Leaderboards are grouping different users according to different criteria. + Leaderboards are grouping different users according to different criteria. links: - title: Overall top 500 url: https://www.codewars.com/users/leaderboard @@ -180,35 +180,35 @@ url: https://www.codewars.com/users/leaderboard/authored - title: Your "personnal" leaderboard (with your allies, in the dashboard) url: https://www.codewars.com/dashboard - + - term: Markdowns (formatting) description: | - CodeWars is responsive to `markdowns`. They allow you to format code or descriptions so that thay are properly readable for other users. + CodeWars is responsive to `markdowns`. They allow you to format code or descriptions so that thay are properly readable for other users. links: - title: TODO url: TODO - + - term: Merge conflicts description: | - When a translation of a kata is published but some changes or done to the description (through the edit panel) before the translation gets approved, it becomes impossible to approve it because of those "merge conflicts". - To resolve this problem, you have to fork the translation and update the description starting with its current (new) version. - + When a translation of a kata is published but some changes or done to the description (through the edit panel) before the translation gets approved, it becomes impossible to approve it because of those "merge conflicts". + To resolve this problem, you have to fork the translation and update the description starting with its current (new) version. + - term: Mutation of the input description: | - To keep it short...: ___Don't mutate the input... Ever___ (eg. don't use sort/append/push/remove/... and alike before doing a copy of the input). - This is about side effects, modifying the arguments (typically lists/arrays, or even strings if they are mutable in your language) sent to your function during the executions. This can have werid consequences, depending on how the tests are written. - Nowadays, most test suites are written in a way to avoid this kind of problem but typically, if you end up passing the fixed tests but failing all the random tests with something along the line of `[your result] should equal []`, you're most likely facing a "mutation of the input" problem. - Hence... Don't mutate the input. - + To keep it short...: ___Don't mutate the input... Ever___ (eg. don't use sort/append/push/remove/... and alike before doing a copy of the input). + This is about side effects, modifying the arguments (typically lists/arrays, or even strings if they are mutable in your language) sent to your function during the executions. This can have werid consequences, depending on how the tests are written. + Nowadays, most test suites are written in a way to avoid this kind of problem but typically, if you end up passing the fixed tests but failing all the random tests with something along the line of `[your result] should equal []`, you're most likely facing a "mutation of the input" problem. + Hence... Don't mutate the input. + - term: Preloaded (code/section) description: | - In a Kata, the preloaded section is code that is executed _before_ the solution of the user. The code hold by this section isn't visible, but every function or variable defined there is accessible through the code. - If you need/want to see the preloaded section of a Kata, open a fork of a solution _after_ you solved it. - + In a Kata, the preloaded section is code that is executed _before_ the solution of the user. The code hold by this section isn't visible, but every function or variable defined there is accessible through the code. + If you need/want to see the preloaded section of a Kata, open a fork of a solution _after_ you solved it. + - term: Progress description: | - Aside of honor points, you gain "progress" by completing Katas (and only that way). Progess is what is conditionning your current rank as a warrior. - + Aside of honor points, you gain "progress" by completing Katas (and only that way). Progess is what is conditionning your current rank as a warrior. + - term: Publishing (kata) description: When you hit "publish" in the edit panel of a kata you created, it enters the beta process and becomes visible to anyone in the [katas search page](https://www.codewars.com/kata/my-languages). The beta process begins at the moment a kata is published. From ba6442f7468c3e534013954d38c8d001ac40d6b6 Mon Sep 17 00:00:00 2001 From: Blind4Basics <32236948+Blind4Basics@users.noreply.github.com> Date: Mon, 13 Jul 2020 20:21:38 +0200 Subject: [PATCH 06/12] Update glossary.yml --- data/glossary.yml | 34 +++++++++++++++++----------------- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/data/glossary.yml b/data/glossary.yml index 4b3b8a46..3a77093b 100644 --- a/data/glossary.yml +++ b/data/glossary.yml @@ -57,7 +57,7 @@ - term: Clan(s) description: | - You can write the name of your clan/company/organisation through your `profile/account settings`. All the member of this clan are automatically recognized as allies of yours, hence are added to your personnal leaderboard in the dashboard. + You can write the name of your clan/company/organization through your `profile/account settings` page. All the members of this clan are automatically recognized as allies of yours, hence are added to your personnal leaderboard in the dashboard. links: - title: Dashboard leaderboard url: https://www.codewars.com/dashboard @@ -71,6 +71,9 @@ - title: Browse through all collections url: https://www.codewars.com/collections +- term: Console + description: Synonym for "output panel" (see below). + - term: Contributor(s) description: User(s) who have either authored, approved, translated or modified a kata in any way (a list of them can be seen in the "Details" page of any kata. @@ -121,12 +124,12 @@ - term: Fork description: | - In the solutions page of a kata, you can see the solutions of other users, and you can `fork` them to suggest modifications/enhancements. - Using the fork panel is the right way to try out a solution of another user, rather than copy it in the trainer of the kata. + In the solutions page of a kata, you can see the solutions of other users, and you can `fork` them to suggest modifications/enhancements (button below each solution). + Using the fork panel is the right way to try out a solution of another user, rather than to copy it in the trainer of the kata. - term: Honor (points) description: | - Honor points are those that are showing up in the top right corner of any codewars page. You can win honor points in different ways (completing katas, up votes on your comments or solutions, translations, creating katas, ...) + Honor points are the score that is showing up in the top right corner, aside of your avatar. You can win honor points in different ways (completing katas, up votes on your comments or solutions, translations, creating katas, ...) - term: Inactive (author) description: | @@ -165,12 +168,10 @@ - term: Language versions description: | - A kata may be available in one or more languages (javascript, python, coq, ...), and for each language, there may be different language versions. Like, Node 8 or Node 10 for JS, or python 3.4.3 or 3.6 for python... - You can choose the language _and_ the language version in the trainer of a kata (amongst the available ones). + A kata may be available in one or more languages (javascript, python, coq, ...), and for each language there may be different versions like Node 8 or Node 10 for JS, python 3.4.3 or 3.6, ... You can choose the language _and_ the language version in the trainer of a kata (amongst the available ones only). - term: Leaderboards - description: | - Leaderboards are grouping different users according to different criteria. + description: Leaderboards are grouping different users according to different criteria. links: - title: Overall top 500 url: https://www.codewars.com/users/leaderboard @@ -183,31 +184,30 @@ - term: Markdowns (formatting) description: | - CodeWars is responsive to `markdowns`. They allow you to format code or descriptions so that thay are properly readable for other users. + CodeWars is responsive to `markdowns`. They allow you to format code, descriptions or comments so that thay are properly readable for other users. links: - title: TODO url: TODO - term: Merge conflicts description: | - When a translation of a kata is published but some changes or done to the description (through the edit panel) before the translation gets approved, it becomes impossible to approve it because of those "merge conflicts". + When a translation of a kata is published but some changes are done to the description (through the edit panel) before the translation gets approved, it becomes impossible to approve it because of those "merge conflicts". To resolve this problem, you have to fork the translation and update the description starting with its current (new) version. - term: Mutation of the input - description: | - To keep it short...: ___Don't mutate the input... Ever___ (eg. don't use sort/append/push/remove/... and alike before doing a copy of the input). - This is about side effects, modifying the arguments (typically lists/arrays, or even strings if they are mutable in your language) sent to your function during the executions. This can have werid consequences, depending on how the tests are written. - Nowadays, most test suites are written in a way to avoid this kind of problem but typically, if you end up passing the fixed tests but failing all the random tests with something along the line of `[your result] should equal []`, you're most likely facing a "mutation of the input" problem. + description: To keep it short...: ___Don't mutate the input... Ever___ (eg. don't use sort/append/push/remove/... and alike before doing a copy of the input). + This is about side effects, modifying the arguments (typically lists/arrays, or even strings if they are mutable in your language) sent to your function during the executions. This can have weird consequences, depending on how the tests are written. + Nowadays, most test suites are written in a way that avoids this kind of problem but typically, if you end up passing the fixed tests but failing all the random tests with something along the line of `[your result] should equal []`, you're most likely facing a "mutation of the input" problem. Hence... Don't mutate the input. - term: Preloaded (code/section) description: | - In a Kata, the preloaded section is code that is executed _before_ the solution of the user. The code hold by this section isn't visible, but every function or variable defined there is accessible through the code. - If you need/want to see the preloaded section of a Kata, open a fork of a solution _after_ you solved it. + In a Kata, the preloaded section is code that is executed _before_ the solution of the user is defined. The code hold by this section isn't visible to the user but every function or variable defined there is accessible to him drugint the executions of his code. + If you need/want to see the preloaded section of a Kata, open a fork of a solution _after_ you solved it and look to the `Preloaded` panel. - term: Progress description: | - Aside of honor points, you gain "progress" by completing Katas (and only that way). Progess is what is conditionning your current rank as a warrior. + Aside of honor points, you gain "progress" by completing Katas (and only that way). Progess is what is conditioning your current rank as a codewarrior. - term: Publishing (kata) description: When you hit "publish" in the edit panel of a kata you created, it enters the beta process and becomes visible to anyone in the [katas search page](https://www.codewars.com/kata/my-languages). The beta process begins at the moment a kata is published. From ddda8bf36a3c7113bf6a2357dfbd77b642f14c18 Mon Sep 17 00:00:00 2001 From: Blind4Basics <32236948+Blind4Basics@users.noreply.github.com> Date: Mon, 13 Jul 2020 20:24:46 +0200 Subject: [PATCH 07/12] Update glossary.yml --- data/glossary.yml | 11 +++-------- 1 file changed, 3 insertions(+), 8 deletions(-) diff --git a/data/glossary.yml b/data/glossary.yml index 3a77093b..2a447d94 100644 --- a/data/glossary.yml +++ b/data/glossary.yml @@ -116,10 +116,9 @@ You can see in the `Social` section of the profile of a user who he is following, who are his followers and who he is ally with. - term: Forfeit (a kata) - description: | - You forfeit a kata when you do one of those actions: + description: You forfeit a kata when you do one of those actions: * you unlock the solutions (through the button in the trainer, for example) - * you enter the edit panel (_warning_: power users may have the possibility to enter the edit panel of some katas. If you do so before you solved it, you actually forfeit it). + * you enter the edit panel (_warning_, power users may have the possibility to enter the edit panel of some katas. If you do so before you solved it, you actually forfeit it). Forfeiting a kata makes you lose the opportunity to gain honor points or progress by completing this kata. - term: Fork @@ -185,9 +184,6 @@ - term: Markdowns (formatting) description: | CodeWars is responsive to `markdowns`. They allow you to format code, descriptions or comments so that thay are properly readable for other users. - links: - - title: TODO - url: TODO - term: Merge conflicts description: | @@ -218,8 +214,7 @@ Most of the times, the user (you) is actually missing something, so use the Question label and not the Issue label, unless you can ___prove___ that the problem you're facing is actually an "issue". - term: Test Driven Development - description: | - Katas are built following this principle: you are provided with specifications and a set of tests, and your goal is to pass those tests (by following the specifications or finding a way to at least pass the tests). + description: Katas are built following this principle: you are provided with specifications and a set of tests, and your goal is to pass those tests (by following the specifications or finding a way to at least pass the tests). acronym: TDD links: - title: Test-driven Development - Wikipedia From 3f18b49af7c52715c0779259a2056d3eba501bff Mon Sep 17 00:00:00 2001 From: Blind4Basics <32236948+Blind4Basics@users.noreply.github.com> Date: Mon, 13 Jul 2020 20:34:23 +0200 Subject: [PATCH 08/12] Update glossary.yml --- data/glossary.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/data/glossary.yml b/data/glossary.yml index 2a447d94..1871b5a8 100644 --- a/data/glossary.yml +++ b/data/glossary.yml @@ -64,7 +64,7 @@ - term: Collections(s) description: | - Collections are sets/libraries of katas that any user can create, for any purpose. All collections are public. + Collections are sets or libraries of katas that any user can create, for any purpose. All collections are public. links: - title: Collections created by one user url: https://www.codewars.com/users/Blind4Basics/authored_collections @@ -117,8 +117,8 @@ - term: Forfeit (a kata) description: You forfeit a kata when you do one of those actions: - * you unlock the solutions (through the button in the trainer, for example) - * you enter the edit panel (_warning_, power users may have the possibility to enter the edit panel of some katas. If you do so before you solved it, you actually forfeit it). + * You unlock the solutions (through the button in the trainer, for example) + * You enter the edit panel (_warning_, power users may have the possibility to enter the edit panel of some katas. If you do so before you solved it, you actually forfeit it). Forfeiting a kata makes you lose the opportunity to gain honor points or progress by completing this kata. - term: Fork @@ -176,9 +176,9 @@ url: https://www.codewars.com/users/leaderboard - title: Top 500 by completed Katas url: https://www.codewars.com/users/leaderboard/kata - - title: Top 500 by authored Katas & translations + - title: Top 500 by authored Katas and translations url: https://www.codewars.com/users/leaderboard/authored - - title: Your "personnal" leaderboard (with your allies, in the dashboard) + - title: Your personnal leaderboard (with your allies, in the dashboard) url: https://www.codewars.com/dashboard - term: Markdowns (formatting) @@ -191,7 +191,7 @@ To resolve this problem, you have to fork the translation and update the description starting with its current (new) version. - term: Mutation of the input - description: To keep it short...: ___Don't mutate the input... Ever___ (eg. don't use sort/append/push/remove/... and alike before doing a copy of the input). + description: To keep it short...: ___Don't mutate the input... Ever___ (eg. don't use sort, append, push, remove, ... and alike before doing a copy of the input). This is about side effects, modifying the arguments (typically lists/arrays, or even strings if they are mutable in your language) sent to your function during the executions. This can have weird consequences, depending on how the tests are written. Nowadays, most test suites are written in a way that avoids this kind of problem but typically, if you end up passing the fixed tests but failing all the random tests with something along the line of `[your result] should equal []`, you're most likely facing a "mutation of the input" problem. Hence... Don't mutate the input. From 445001c469a7f9226708194e10ef44482d3274e4 Mon Sep 17 00:00:00 2001 From: Blind4Basics <32236948+Blind4Basics@users.noreply.github.com> Date: Mon, 13 Jul 2020 20:51:02 +0200 Subject: [PATCH 09/12] Update glossary.yml --- data/glossary.yml | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/data/glossary.yml b/data/glossary.yml index 1871b5a8..2b3aba3f 100644 --- a/data/glossary.yml +++ b/data/glossary.yml @@ -116,9 +116,10 @@ You can see in the `Social` section of the profile of a user who he is following, who are his followers and who he is ally with. - term: Forfeit (a kata) - description: You forfeit a kata when you do one of those actions: - * You unlock the solutions (through the button in the trainer, for example) - * You enter the edit panel (_warning_, power users may have the possibility to enter the edit panel of some katas. If you do so before you solved it, you actually forfeit it). + description: | + You forfeit a kata when you do one of those actions: + * You unlock the solutions (through the button in the trainer, for example) + * You enter the edit panel (_warning_, power users may have the possibility to enter the edit panel of some katas. If you do so before you solved it, you actually forfeit it). Forfeiting a kata makes you lose the opportunity to gain honor points or progress by completing this kata. - term: Fork @@ -191,7 +192,8 @@ To resolve this problem, you have to fork the translation and update the description starting with its current (new) version. - term: Mutation of the input - description: To keep it short...: ___Don't mutate the input... Ever___ (eg. don't use sort, append, push, remove, ... and alike before doing a copy of the input). + description: | + To keep it short...: ___Don't mutate the input... Ever___ (eg. don't use sort, append, push, remove, ... and alike before doing a copy of the input). This is about side effects, modifying the arguments (typically lists/arrays, or even strings if they are mutable in your language) sent to your function during the executions. This can have weird consequences, depending on how the tests are written. Nowadays, most test suites are written in a way that avoids this kind of problem but typically, if you end up passing the fixed tests but failing all the random tests with something along the line of `[your result] should equal []`, you're most likely facing a "mutation of the input" problem. Hence... Don't mutate the input. @@ -214,7 +216,8 @@ Most of the times, the user (you) is actually missing something, so use the Question label and not the Issue label, unless you can ___prove___ that the problem you're facing is actually an "issue". - term: Test Driven Development - description: Katas are built following this principle: you are provided with specifications and a set of tests, and your goal is to pass those tests (by following the specifications or finding a way to at least pass the tests). + description: | + Katas are built following this principle: you are provided with specifications and a set of tests, and your goal is to pass those tests (by following the specifications or finding a way to at least pass the tests). acronym: TDD links: - title: Test-driven Development - Wikipedia From e964b5a17a53944cfac4ecc4559b9685f87e2910 Mon Sep 17 00:00:00 2001 From: Blind4Basics Date: Mon, 13 Jul 2020 18:51:42 +0000 Subject: [PATCH 10/12] Prettier --- data/glossary.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/data/glossary.yml b/data/glossary.yml index 2b3aba3f..3317849c 100644 --- a/data/glossary.yml +++ b/data/glossary.yml @@ -73,7 +73,7 @@ - term: Console description: Synonym for "output panel" (see below). - + - term: Contributor(s) description: User(s) who have either authored, approved, translated or modified a kata in any way (a list of them can be seen in the "Details" page of any kata. From 773db800a7f609a578190f3ca001ba1dbd4f43f9 Mon Sep 17 00:00:00 2001 From: Blind4Basics <32236948+Blind4Basics@users.noreply.github.com> Date: Mon, 13 Jul 2020 20:56:59 +0200 Subject: [PATCH 11/12] Update glossary.yml --- data/glossary.yml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/data/glossary.yml b/data/glossary.yml index 3317849c..3f293a62 100644 --- a/data/glossary.yml +++ b/data/glossary.yml @@ -32,7 +32,8 @@ ## ``` - term: Abandoned kata - description: Kata whose the author is not active anymore. + description: | + Kata whose the author is not active anymore. - term: Active (author) description: Author who has been connected to Codewars during the last 30 days. From 32c67b8e99c943ec4af16b5ab0095d4eda73007e Mon Sep 17 00:00:00 2001 From: kazk Date: Mon, 13 Jul 2020 13:18:22 -0700 Subject: [PATCH 12/12] Fix capitalization of Codewars --- data/glossary.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/data/glossary.yml b/data/glossary.yml index 3f293a62..40b751b7 100644 --- a/data/glossary.yml +++ b/data/glossary.yml @@ -185,7 +185,7 @@ - term: Markdowns (formatting) description: | - CodeWars is responsive to `markdowns`. They allow you to format code, descriptions or comments so that thay are properly readable for other users. + Codewars is responsive to `markdowns`. They allow you to format code, descriptions or comments so that thay are properly readable for other users. - term: Merge conflicts description: |