Interesting. I'm pretty sure I didn't get credit, as the translation is now under "Closed" on my profile, rather than "Published." Not sure if there's a way to check?

@Steffan153 I did try to fork it, but it always seemed to grab the old description and it wasn't going to fix the problem. When you say "fork it," can you be more specific about what and how to fork? I'd love to avoid this issue in the future. :-)

Can you explain the intention behind deprecating my fork and publishing your own?

Man... this UI is so confusing. It looks like I can't create a new translation now that one for TypeScript exists. Trying to create a fork didn't seem to solve the problem either. Any tips are welcome.

I copied the raw description off the current kata and pasted it into this one, hopefully that fixes the issue?

Updated, I think. LMK if that didn't work.

Figured it out and fixed the tests. It was missing an it block.

I'm a bit confused, could you help out? I don't see how it has failed tests... This is my first time trying to provide a translation.

How is this considered best practices?

I love the use of .fill, I've never seen that one before, nice! I think this one is the best balance of brevity with readability.

Can you explain your reasoning there? Why should the query have to be edited if the table's column set changes?

ARRRRRGGGGHHHH why didn't I think of that 😂

I was just trying to be helpful by suggesting improvements to the description. I don't see any reason to accuse me of not having common sense. What may seem obvious to you may not be to others.

Nicely done here, I think it's the most easy-to-understand iterative solution.

Interesting fact: using the same regex, but with .match, causes tests to fail, as in:

return coordinates.match(/^(-?((\d|[0-8]\d)(.\d+)?)|90),\s?(-?((\d\d?|[01][0-7]\d)(.\d+)?)|180)$/);

Any idea why?