Hello, @Daniel-Ioannou 👋🏽

I want to commend you, first of all, for your awesome package. It has come in handy in several of my projects. Here's just a token of appreciation from my end 😄

Just added styling options for the border-radius and the search field, in case developers need to customize those. I also updated the documentation to cover the changes and corrected a few typos.

Please let me know if any changes are required for this PR to be merged. 🙏🏽

Thank you.

I'm working on an app that's a part of an existing system, where only the name of the country is stored in the database. I would like to be able to parse and translate this string to the localized name of the country, so that I can show the previously selected country in the app.

This is my take on a solution, and I wondered if this is something you would want to add to the package, since the package already provides the translations.

There are some things in there that may not be optimal, like the duplication of supported locale and mapping of translation files (see the ToDos). There may be some solution to this, but these methods are currently private or in another way not accessible inside the CountryLocalizations class. I also guess that the wrong country may be returned if two languages uses the same word for different countries. I have no idea if that might be the case.

I've ran the worst case scenario parsing, and it seems like it takes about half a millisecond on average over 100.000 runs on my Samsung Galaxy S10+. I'm guessing that we might see a couple of milliseconds of parse time on an older device, and more if a lot of translations are added down the line. There are probably some ways to make it more efficient, but i thought that the current solution is the most user friendly. It's probably best to leave the parsing out of the build method anyways.

Tips for changes and improvements are welcome.

According to Norm ICAO 9303, nationality codes are defined for machine readable documents with these specifications https://www.icao.int/publications/Documents/9303_p3_cons_en.pdf These are the codes stated in official documents MRZs.

Added them here as this is the most prominent country picker package that I would like to use for country picking in tourist forms to be submitted to immigration services.

As mentioned in https://github.com/Daniel-Ioannou/flutter_country_picker/discussions/57: I need "world wide" option in my app. @Daniel-Ioannou If you like it we can add it to the library.

TODO

• [x] Update Country.parse method to return world wide.
• [x] Translate "World Wide" if Daniel likes it.

Hi, Great package but could you tell me if you plan to improve display by making the bottom sheet with adaptive height to content or at least being able to set the height to a specific height?

Hello @Daniel-Ioannou 👋🏽

Thank you for providing this package - I've found it so awesome.

I recently needed the Arabic locale and found that it was missing from the package, so I decided to write the code for it and submit a PR.

Please let me know if I need to do anything else to speed up the approval and merging of this PR.

Thank you, sir.

Hi. I've made an app that uses localizations, as described in the Flutter docs. I've tried to run the example project, and that implementation works. However, when implemented using the official Flutter guide, it doesn't work. I've added a complete runnable project that demonstrates this issue.

Other localized strings works as intended , but the static CountryLocalizations? of(BuildContext context) method in country_localizations.dart returns null, which means that none of the strings in the package are translated. I'm not completely sure what causes this issue, because the inner workings of the Flutter localizations still remains a mystery to me.

An example of a workaround fould be to return CountryLocalizations(Localizations.localeOf(context)) instead of Localizations.of<CountryLocalizations>(context, CountryLocalizations), but I don't know if this comes with some kind of cost. Thoughts?

…the same structure as the country flags.

Did a minor change in "lib/src/country_list_view.dart"
Widget _flagWidget(Country country)

As I could have problems loading the asset worldwide.png at some times I changed so worldwide as well uses emoji as the rest of the country flags.

In this version:

• Fix Eswatini name
• Fix Italy code at Turkish localization
• Add optional argument for showing "World Wide" option at the beginning of the list

  showCountryPicker(
    context: context,
    showWorldWide: true,
    onSelect: (Country country) => print('Select country: ${country.displayName}'),
  );
  

Following the example of a old similar library, you can add static methods country_pickers

Example

  Country _selectedDialogCountry = CountryPickerUtils.Utils.getCountryByIsoCode('MF');

  void _openCountryPickerDialog() =>  showCountryPicker(
    context: context,
    //Optional.  Can be used to exclude(remove) one ore more country from the countries list (optional).
    // exclude: <String>['KN', 'MF'],
    favorite: <String>['SE, US'],
    //Optional. Shows phone code before the country name.
    showPhoneCode: true,
    onSelect: (Country country) {
      setState(() => _selectedDialogCountry = country);
    },
    // Optional. Sets the theme for the country list picker.
    countryListTheme: CountryListThemeData(
      // Optional. Sets the border radius for the bottomsheet.
      borderRadius: BorderRadius.only(
        topLeft: Radius.circular(40.0),
        topRight: Radius.circular(40.0),
      ),
      // Optional. Styles the search field.
      inputDecoration: InputDecoration(
        labelText: 'Search',
        hintText: 'Start typing to search',
        prefixIcon: const Icon(Icons.search),
        border: OutlineInputBorder(
          borderSide: BorderSide(
            color: const Color(0xFF8C98A8).withOpacity(0.2),
          ),
        ),
      ),
    ),
  );

   Text("+${_selectedDialogCountry.phoneCode}"), -> view user

change utils

   import 'country.dart';
import 'res/country_codes.dart';

class Utils {
  static List<Country> _countryList = countryCodes.map((country) => Country.from(json: country)).toList();

  static String countryCodeToEmoji(String countryCode) {
    // 0x41 is Letter A
    // 0x1F1E6 is Regional Indicator Symbol Letter A
    // Example :
    // firstLetter U => 20 + 0x1F1E6
    // secondLetter S => 18 + 0x1F1E6
    // See: https://en.wikipedia.org/wiki/Regional_Indicator_Symbol
    final int firstLetter = countryCode.codeUnitAt(0) - 0x41 + 0x1F1E6;
    final int secondLetter = countryCode.codeUnitAt(1) - 0x41 + 0x1F1E6;
    return String.fromCharCode(firstLetter) + String.fromCharCode(secondLetter);
  }

  static Country getCountryByIsoCode(String isoCode) {
    try {
      return _countryList.firstWhere((country) => country.countryCode.toLowerCase() == isoCode.toLowerCase(),
      );
    } catch (error) {
      throw Exception("The initialValue provided is not a supported iso code!");
    }
  }

}

If the country is parsed from .parse(...) or .tryParse() accessing nameLocalized throws a LateInitialisationError. Probably not an easy fix since a context is needed to get the localized name but maybe there is a way to do it.

Is it possible to extend this project and also provide a language picker? The use case is to provide flutter app translation support by selecting a language from the picker

I came upon a scenario where I only needed to include 3 countries and didn't know how to go about it. The temporal solution was to filter out the countries which were not needed and pass it to the exclude field. It worked but I think it isn't efficient. So I just decided to add this feature.

Hi Daniel,

Would it be possible to add Latinized search by country name? The https://pub.dev/packages/latinize is a good option to "to convert accents (diacritics) from strings to latin characters" before search.

I've forked and implemented using latinize: ^0.1.0-nullsafety.0. It is doing good here! The fork is at https://github.com/cc-nogueira/flutter_country_picker.

Thanks.