-
-
Notifications
You must be signed in to change notification settings - Fork 230
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Null type checks is not considered by the tests length #63
Comments
See my example const getKey = value => (value === null ? 'null' : typeof value);
/*
const getKey = value => {
if (value === null) return 'null';
return typeof value;
}
*/
const countTypesInArray = data => {
const hash = {};
for (const item of data) {
const key = getKey(item);
if (hash[key]) hash[key] += 1;
else hash[key] = 1;
}
return hash;
}; |
Test it on input data |
@PavelZubkov your solution seems to work just fine. Regarding my function: yeah, you're right, that's my bad. I haven't mentioned the case when arr consists of only 1 null. But I still didn't find a better solution that won't use a ternary operator. The following one in some terms is the same as yours:
However, I've decided to make a new array and only after that perform counting of types. I think that on big amounts of data it'll perform slower, but it's simpler to read (IMO). |
There is a problem with countTypesInArray function (
4-count-types.js
). The tests require a solution to be 200 signs max, but in this case, we kinda lose the check fornull
s.As you know
null
in JavaScript has a type of object. Thus, the implementation you require will count objects but not nulls. So, the function is not suitable for checking all the JS types.I clearly understand that such a check can be done using a ternary operator but it's not convenient and intuitive enough.
The implementation below considers this JS's quirk:
So, maybe you should consider an option for making tests a little bit more loose for
null
checks.The text was updated successfully, but these errors were encountered: