Add BCP47 parser

[miniBill]

No description provided.

[miniBill]

The type that is currently called Country and described as ISO 3166-1 country code is called region in BCP47, because it could also be an UM M49 [1] numeric code.

My proposal is to rename it to Region.

[1] https://en.wikipedia.org/wiki/UN_M49

EDIT: this has now been implemented in #3

[dillonkearns]

Looks good other than the two comments I made and the elm-review errors in the CI. I'll merge and release once that's resolved. Thanks for the PR @miniBill!

[miniBill]

The NoModuleOnExposedNames errors are false positives, I can suppress them?

You said you wrote two comments but I can't see them?

With regards to releasing, I think it's valuable to first decide whether to merge #3 in the next major bump or not

[dillonkearns]

@miniBill is this the problem that's causing the false positives? sparksp/elm-review-imports#127

I don't like the idea of using suppressed errors for bugs - I try to avoid suppressing errors, I see the main use case for those as being adopting a rule in a large codebase where you can't fix everything at once. I'd rather turn off the rule temporarily with a comment that links to the GitHub issue and explains that it can be re-enabled once that fixed. Would you be up for adding that in this PR?

With regards to releasing, I think it's valuable to first decide whether to merge #3 in the next major bump or not

Good idea, I'll hold off on releasing until we've discussed that.

[dillonkearns]

You said you wrote two comments but I can't see them?

I can see them from this page #2.

I see the comments like this in that page:

[miniBill]

(notice how it says "Pending" on top, it means they are not visible to me yet)
Both comments make sense, will do!

[dillonkearns]

(notice how it says "Pending" on top, it means they are not visible to me yet)

Ah yes, sorry about that, I sent them off for review so should be good now!

[miniBill]

Made the changes requested

[dillonkearns]

Looks good, thank you for the PR @miniBill!

I'll let you follow up with #3 before I cut a new release.