I’m tired of writing custom logic to interpret country inputs and want a single resolver that returns iso2, iso3, and dial together.

Provide a single country resolver that takes a user-provided country input and returns a normalized result containing ISO2, ISO3, and dialing code. This removes the need for repeated, custom parsing and mapping logic across different parts of an application.

This feature introduces a unified country resolver designed to standardize how country inputs are interpreted and normalized. It accepts a country input (for example, a value provided by an end user or received from an external system) and returns a consistent object containing ISO2, ISO3, and dial code together. The primary purpose is to eliminate duplicated, custom logic that teams often maintain to translate country names or codes into multiple standardized formats. By returning all three values in one response, it simplifies downstream workflows such as storing normalized country data, building consistent analytics dimensions, and powering phone-number or contact flows. It also reduces the risk of mismatched mappings where one part of the system uses ISO2 while another uses ISO3 or a separate dialing-code table. A single resolver makes integrations cleaner by providing one interface for country normalization regardless of where the input originates. It supports more maintainable codebases by centralizing the mapping logic in one place rather than scattering it across services and clients. This is especially useful in signup forms, address capture, CRM imports, customer support tools, and data pipelines where the same country fields appear repeatedly. The expected outcome is faster implementation, fewer edge-case bugs, and more consistent country data throughout the product.