Retired
Shorten composite Full Name (retired)
Loading description...
Strings
Regular Expressions
Fundamentals
View
This comment has been reported as {{ abuseKindText }}.
Show
This comment has been hidden. You can view it now .
This comment can not be viewed.
- |
- Reply
- Edit
- View Solution
- Expand 1 Reply Expand {{ comments?.length }} replies
- Collapse
- Spoiler
- Remove
- Remove comment & replies
- Report
{{ fetchSolutionsError }}
-
-
Your rendered github-flavored markdown will appear here.
-
Label this discussion...
-
No Label
Keep the comment unlabeled if none of the below applies.
-
Issue
Use the issue label when reporting problems with the kata.
Be sure to explain the problem clearly and include the steps to reproduce. -
Suggestion
Use the suggestion label if you have feedback on how this kata can be improved.
-
Question
Use the question label if you have questions and/or need help solving the kata.
Don't forget to mention the language you're using, and mark as having spoiler if you include your solution.
-
No Label
- Cancel
Commenting is not allowed on this discussion
You cannot view this solution
There is no solution to show
Please sign in or sign up to leave a comment.
JS starting code has an erroneous extra
{
.I'm a UK guy. We use Mr. Not sure what the Wikipedia article was saying with that, but it's not right. Likely the same with the suffixes (though it's so rare to see one, I can't speak to experience with that.) I think it just depends on the situation, the context. A TV channel might drop the dots, a legal document might keep them, etc.
Just giving an example isn't enough. There is some amount of spec below that, but some things are left out--making it an incomplete spec. And making the resulting code kinda brittle, that passes only the tests you've written but it would fail other real-world cases.
prefixes -> [ 'Mister', 'Mr.', 'Mr', 'Madame', 'Mrs.', 'Mrs', 'Miss', 'Ms.', 'Ms' ] suffixes -> [ 'Senior', 'Sr.', 'Sr', 'Junior', 'Jr.', 'Jr' ]
Like "Junior" and "Jr". Must be to a map from what may be translated and the final word and no all the thing together.
If you submmit a pull request this way your partners of the team will say bad things of you...
I think it's just to show you what counts? Or something? They should just put it in the spec, in my opinion.
It's not mentioned anywhere that prefix/suffix checking should be case-insensitive.
Random tests:
It is unclear how the spec
Every element of the returning string should be capitalized
should be interpreted with name parts containing multiple uppercase letters.And in the end, no matter what the expected behaviour is, it should be in the fixed tests to make sure it's tested. Sometimes it does not appear in the random tests.
These two statements in description contradict with each other. It should be "one or more First Name(s)".
Preloaded
prefixes
andsuffixes
are arrays like this:How are we supposed to comprehend this data structure? When I see
Mister
I do not know what it's supposed to map to, unless I refer to the expected result or the description. (Or in other words, these preloaded arrays are pretty useless.)In the tests there is variant with 'jr', but in description is said that can be only 'Jr' variant.
This comment has been hidden.
You're perfectly right. Thanks
Got the issue. Thanks.