Beta
Count unique shapes
Loading description...
Geometry
Arrays
Algorithms
This comment has been reported as {{ abuseKindText }}.
Show
This comment has been hidden. You can view it now .
This comment can not be viewed.
- |
- Reply
- Edit
- View Solution
- Expand 1 Reply Expand {{ comments?.length }} replies
- Collapse
- Spoiler
- Remove
- Remove comment & replies
- Report
{{ fetchSolutionsError }}
-
-
Your rendered github-flavored markdown will appear here.
-
Label this discussion...
-
No Label
Keep the comment unlabeled if none of the below applies.
-
Issue
Use the issue label when reporting problems with the kata.
Be sure to explain the problem clearly and include the steps to reproduce. -
Suggestion
Use the suggestion label if you have feedback on how this kata can be improved.
-
Question
Use the question label if you have questions and/or need help solving the kata.
Don't forget to mention the language you're using, and mark as having spoiler if you include your solution.
-
No Label
- Cancel
Commenting is not allowed on this discussion
You cannot view this solution
There is no solution to show
Please sign in or sign up to leave a comment.
This comment has been hidden.
After 2 years it seems the description si broken and is not showing the Peaces.
I found a local solution by inspecting the cells (html td's), and creating a new css style rule fot the td.w, set a color to the background for example: td.w { bacground-color: aqua; }
technically,
<style>elements are only supposed to be present in the<head>element, so I'm not surprised that it stopped working. I replaced all of theclassattributes by inlinestyleattributes, which fixes the descriptionmy hypothesis is that the Codewars' markdown renderer supported
<style>declarations at some point but stopped doing so after an update. if someone has a workaround they should edit the description, as the inline CSS blows up the size of the description's sourceRandom tests: modifying the input changes the expected result.
Fixed, now the expected result does not change despite any changes in the input array
Suggested tags:
arrays, geometry, algorithmsError messages are not useful. You have to test the tuple as a whole, not item by item.
The user wants to see something like this:
actual value (1, 0) does not equal expected value (3, 5)Fixed test Assertions as suggested
This comment has been hidden.
Your kata is sent back to Draft, once you solve these issues, you can republish the kata back to beta.
Thanks for pointing that out. Added random tests