lcid

The dataset used seems to be both incomplete and unnecessarily limited: I just extracted the current list of locales from the Microsoft LCID 16.0 reference document, which contains 862 individual locales—see this gist for the full JSON output. It contains separate fields for the language name ("English"), the location ("United States"), the LCID ID ("1033"), and the locale tag ("en-US"). Short locales ("en") have the location set to null; locales without an assigned LCID have the ID set to null. Using this info, you can get a lot more information that might be useful to applications, at the cost of a larger JSON file. Would you be open to incorporating that data set into this package? Might even be sensible to just have several conditional exports with different levels of included details.

When calling or , the methods can return but the types were not indicating that. All tests pass. This is the first time I am contributing to an open source package. I probably forgot a few things. Just let me know and I will happily comply. :) Fixes #14

Those two methods can return since any or any can be passed in. !Screenshot 2023-01-16 at 13 20 13 I opened a PR with a proposed solution here.