๐Ÿ‡ฎ๐Ÿ‡ณIndia @kkalaskar

Pune
Account created on 3 July 2014, over 10 years ago
#

Recent comments

๐Ÿ‡ฎ๐Ÿ‡ณIndia kkalaskar Pune

Created patch with following change

Existing :-

   $action = $form_state->getValue('action');
    if (empty($action)) {
      $form_state->setErrorByName('', $this->emptyActionMessage());
    }

Updated :-

    $action = $form_state->getValue('action');
    if (strlen($action) === 0) {
      $form_state->setErrorByName('', $this->emptyActionMessage());
    }
๐Ÿ‡ฎ๐Ÿ‡ณIndia kkalaskar Pune

typo: Cookies.set, Cookies.get and Cookies.remove needs to update in doc as well

๐Ÿ‡ฎ๐Ÿ‡ณIndia kkalaskar Pune

Rerolled patch for 8.x-2.0-alpha9

๐Ÿ‡ฎ๐Ÿ‡ณIndia kkalaskar Pune

@harshit_ghediya

Specifying the core_version_requirement
The core_version_requirement key in *.info.yml files for modules, themes, and profiles now supports semantic versioning as implemented by the Composer project. This allows modules, themes, and profiles to also specify that they are compatible with multiple major versions of Drupal core.

For example, a module that is compatible with Drupal 9 and Drupal 10 can have a info.yml file like this

name: My Module
type: module
core_version_requirement: ^9 || ^10
For example a module that is compatible with Drupal 8 and Drupal 9 can have a info.yml file like this

name: My Module
type: module
core: 8.x
core_version_requirement: ^8 || ^9
This specifies that the module is compatible with all versions of Drupal 8 and 9. The core: is required here because Drupal Core versions before 8.7.7 do not recognize the core_version_requirement: key.

https://www.drupal.org/docs/develop/creating-modules/let-drupal-know-abo... โ†’

Production build 0.71.5 2024