Drupal 8+'s .info.yml version constraints for dependencies are weird! The Drupal.org module development .info.yml docs version constraints for dependencies section informs that these constraints are custom Drupal and differ from composer
Welcome to my Blog, happy reading! ツ
Defining a proper Schema for a custom field Type in Drupal 8+ doesn't seem to be very well documented yet. Luckily, the core gives us some good examples to start from. For that reason, you should have a look into the core modules that
When developing custom modules for Drupal, translating the user interface strings can not benefit from the localize.drupal.org infrastructure, like for contrib modules. So you need a way to provide these UI translations in your custom
Should you run into the situation where you need to reset the module config to the installation state (for what ever reasons), then this snippet might help you: \Drupal::service('config.installer')->installDefaultConfig('module', $module)
Do you see one of the following errors in your Drupal 8+ Status Report? Mismatched entity and/or field definitions The XXX field needs to be updated. The XXX field needs to be uninstalled. This is caused by mismatch in the field (storage)
Drupal Form API doesn't offer a native HTML type="reset" button known from the W3C: https://www.w3.org/TR/2012/WD-html-markup-20121025/input.reset.html So if you ever need one, this might be a good starting point in Drupal 8+: 'reset' => [
This post saved you a lot of time and headache?
Then I'd be very happy about a delicious coffee! Or a helpful book from my wish list.