There doesn't seem to be a test for the color argument.

My solution was able to pass even though it always set the cells to '⬛'

na, I used your link only x)

ah perhaps it's wiki french page?

I undertsand but I've choosen 2d array of char because it's easier to plot pixels

But to show result I think it's more clear as unique string with \n because it looks like a screen of big pixels.

The sample code as already the good return written

I've done some text modification

Thanks for feed back

not really fond of the idea, but that was worth of it.

I don't feel like I've read the same article than you, there... :o

well, was interesting. I didn't go the simplest way about the geometry, tho... XD

• your logs are misleading, for now, even if the intent is good: which one is eactual and which one is expected?
• looking at the logs of the 25x25, at 10,13 for the center... looks like what you said about the axis is totally wrong, isn't? => x is horizontal going right, and y is vertical going... down!? See, talking about "is rows... us columns" doesn't tell if you're talking about the indexes of the axis...

consider this one as a very strong suggestion:

in the sample tests, you should show the strings using multiline ones. This way the expecte'd result is immediatly visible from the user.

x are columns

• you need to precise that x is going down, just like usual in a 2D array.
• the description and the tests are expecially confusing about wht should be returned: string? array?
  • string is visible in the sample tests, but you use an unknown custom assertion function
  • the description doesn't say anythig really clear about that
  • the assertions are showing that 2D arrays are tested... => what the user is supposed to return, actually?
    => you have to be pretty clear about that

Because the algorithm doesn't need it

Hi,

why the restrictions...? I don't feel like this enhance a,ything at all...

eval was not desactivated because it's not really interessing here. It's not like in some kata where the goal is to eval arithmetic expression.

It seems you've not properly forbided them.

Tests updated. Code checks tests fails now