Skip to content
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

Phone number: Correct the format #2317

Merged
merged 1 commit into from
Sep 30, 2023
Merged

Phone number: Correct the format #2317

merged 1 commit into from
Sep 30, 2023

Conversation

iHiD
Copy link
Member

@iHiD iHiD commented Sep 6, 2023

Context: https://forum.exercism.org/t/nanp-phone-numbers/7179/1

This shouldn't change any tests, so I think it's pretty safe to merge.

@iHiD iHiD requested a review from a team as a code owner September 6, 2023 23:46
@ErikSchierboom
Copy link
Member

This shouldn't change any tests, so I think it's pretty safe to merge.

True, but most of the tests use the old format, so that might be a bit weird.

@@ -11,12 +11,14 @@ The first three digits of the local number represent the *exchange code*, follow
The format is usually represented as

```text
(NXX)-NXX-XXXX
NXX NXX-XXXX
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We might show both that are often used...

The tests are not going to differentiate in a way that errors, but will present it as a cleaned version.

Here we are showing what is "usually" represented, and I might think that

(NXX) NXX-XXXX

And

(NXX)NXX-XXXX

are pretty evenly tied in the usual use.

I totally agree with using either with parenthesis or or dash to separate the area code from either or both sides of that, never both at the same time.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could also change "usually" to "sometimes" and not worry about what is commonly used where 😄

@iHiD
Copy link
Member Author

iHiD commented Sep 7, 2023

In response to the comments in general, I think the point is that the tests provide different formats but really the input format is irrelevant - what matters is that it gets normalised. So I think we should make the description actively generic, rather than more specific. If that makes sense?

@ErikSchierboom
Copy link
Member

Totally agree

@BethanyG BethanyG merged commit 957c0c2 into main Sep 30, 2023
8 checks passed
@BethanyG BethanyG deleted the iHiD-patch-1 branch September 30, 2023 19:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants