Skip to content

Resolve #3394102: Introduce custom entities instead of taxonomy terms for countries

Simon Bäse requested to merge issue/language_country_negotiation-3394102:3394102-custom-country-entities into 1.0.x

Closes #3394102

WARNING These changes are not backwards compatible. Please uninstall the module and reinstall with changes from MR. See README for usage!

@AnnaDemianik This MR introduces the custom entity type Country (translatable and fieldable). Some notes:

  • removed dependency to taxonomy terms including configuration
  • removed continent functionality (we can readd this functionality through fields in a submodule)
  • adjusted tests for removed continents
  • added constraints for the country base fields
  • added selection handler for configurable languages entity reference
  • added form for country entity
  • added country list builder at Configuration > Region and language > Countries (here is also the field configuration)
  • translatability is a little funny because the custom entity does not provide a canonical URL, that is why we have a hook to add the content translation routes in the module file, if the content_translation module is activated
Edited by Simon Bäse

Merge request reports