Arrow function, great solution!!

Cannot reproduce, closing ~~

thanks, it's fixed now

You can make the decision process to be in the regex itself. I'll try to improve error messages so you can get some more info.
Your solution could benefit from the next regex concepts: groups, groups in replacement, |, &. Let me know any futher problems.

Maybe the problem is with the browser..

Closing the issue.

Unfortunately the Kata and its Test Cases cannot be modified when it is already completed more than 500 times. :(

Shall I close the issue?

Hm I think it's more because there are already have more then 500 users who finished it, so the kata gets locked. Not sure if that should count for translations as well or if the translation also has already reached that threshold...

It seems codewars doesn't allow the translation author to update the translation.

I've tried to provide an update translation, but than jhoffner responded "Looks like this is a bug to be able to create this translation. The kata already supports java." and then the conversation ended.

So once the translation is there, it's up to the kata's original author to update it.

Thanks bkaes. I think that would count. Is there a possibilitiy the test cases can be updated to include the suggested workaround in the link you provided?

Yes, I was under the impression I could fork the current Java translation and offer improvements/changes to it. There have been comments by other users on suggested changes and, since I created the translation, I thought I would try to address them. Is the original author the only one that can update the original kata and any approved translations?

Looks like this is a bug to be able to create this translation. The kata already supports java.

As a long time Java developer, I'll add to Darnor's statment, this is an example of poor design in the Java world.

Access control and defensive code are taken very seriously in professional environments.

The mantra is:

• Never make public what can be package protected.
• Never make package protected what can be protected.
• Never make protected what can be private.

In this case, public access getters methods would be provided, but the members would be private so that they cannot be altered without the 'consent' of the class via a public setter method.