Hi again,
I had put the spoiler flag because it had some spoiler details imo,
Im about to step out but ill make those changes when i get back.

In any case thank you again for your time.

Also NOT related but still valid..
This kata has been sabotaged as far as rating difficulty!
Someone on ur team rated this a 8 kyu! (the kata claimed to be similar by you is a 4 kyu)
This is def not a 8 kyu and as you know it is more involved than the other.

If this was not from a member on your team it would not be a issue with me.
However since this was from a member on your team i feel like:
Getting a bad rating as far as satisfaction is concerned is fine (to each his own)
but to be that disingenuous about the dificulty of the kata i feel is wrong!

you are trying to split a variable that is undefined or is == ''.
you have to handle those cases before you try to split or you will get that error.

regarding the dif enough.. i didnt think this would of been a issue at all.. as per the sites wiki page reads..

How to not step on the minefield of duplicate katas
Search for keywords to see if someone has done the idea before

As we all know, before you even engage your enemies, you need to send scouts forward.

For example, while Peano and Church numbers are definitely not easy, as the search results clearly shows, they've been done many times already.

In a way, knowing the katas in the wild is very similar to knowing your enemies: you get to see how others write the same kata, other people's (sometimes) brilliant solution in these katas.

Then, maybe you can decide whether to retreat, or make a harder version of the kata as return if you feel the existing one is too lackluster/easy.

The last part i understood as making something harder is not a duplicate and is welcomed... maybe im naive idk... but to me handling big numbers in JS is def harder than the alternative and all the others hoops i made for them to jump through as well...

Thanks Again Sir.. Also gona check out your solution and thanks for spending ur time on this and helping me find those bugs!

Regarding being lenient. I find you to of treated me very fair.. Its been a pleasure interacting with you Sir!
But i do hope you understand how frustrating it must be to hear that... This kata has as much similarity to the others as adding 2 numbers has to adding 2 big numbers as string... clearly a big dif in the way u must handle them... and that is the reason i created this to handle those big numbers.. cause in english speaking terms saying things like 100 vigintillion is no biggie but it is when u gotta handle that in a math term where there are limits on how big a number can be and how the language handles these limits under hood...

No to mention the kata that is mentioned to be similar has a lot more similarities to https://www.codewars.com/kata/53c94a82689f84c2dd00007d u can easily make one solution work on the other.. That is not the case here. But im sure u know this and thats prob why u treated me fair...

That is because codewars has a submit bug... at least through my experience.. here is when the bug happens...
when u solve a kata and forget to hit submit but click on view solutions... it wont give u the nag about forfit so u think its all fine until u find out for some reason it will not post ur solution after that has happened... this has happened to me 2x so far.. ive only been here for a lil over a month so.. idk really you all would know better. Im big on pattern recognition and thats what ive noticed..

I took the time to create this because i seen a need for it and i thought it would be interesting to solve.. I also enjoy these kind of katas and that is why i was inclined to do this.. The big numbers in Js have always been a problem.

I will say... this is my first Kata and from the amount of work i put into it i was expecting people to be a lil more welcoming... The fact that you are saying people seem to judge it b4 even understanding what its requirements are especially when dealing with big numbers..is SAD! and it will prob be my first and last kata that i create.. i didnt do this for me... i thought that is how u contribute to the site. I tried very hard and gave this much thought i would never of put in all this work if i thought it was a dup... Anyways Thanks for taking the time to help me find these bugs i appreciate that.

I think i just fixed the prob can u try again and sorry 4 the wait went to lunch and only got back 10 or so mins ago.

@Blind4Basics Howdy!

I also just cut the tests back from the 2300+ to about 1200 now let me know if that helps out your solution with the timeout issue

hi ok ive found the bug and it is now corrected thank you :)
please try again also might wanna hit reset just in case.
let me know if you find any other issues please.

:p it def should not lol.. thank you for finding this bug.. im working on debugging now will keep you posted.

Regarding performance Your code should not run into any timeout issues.(my solution is running all 2000+ tests in 1.3s)
I believe the timeout is set to 12s by default.. However i can cut the tests down to about 1000 tests but imo that wont help if your code is timing out its most likely cause of some logic or recursive issue. You mentioned it was towards the end of tests and that is where the real big numbers are at including extreme large decimals. Give it a bit of thought and let me know how it goes and if you are still timing out ill cut the tests down to 1000 and u can try again to see if it makes a dif.

Hi and Thank You for taking time out of your day to spend on this Kata..
Ive fixed the thrity-six typo in the static tests, regarding the other issue i am not sure where you are seeing that first error do you happen to know the input that was sent?

np :) and thank you for your time! i will be back in a few hours. thanks again!