Skip to content
Snippets Groups Projects

Issue #3238915: Refactor (if feasible) uses of the jQuery ready function to use VanillaJS

Closed Issue #3238915: Refactor (if feasible) uses of the jQuery ready function to use VanillaJS
Closed Harumi Jang requested to merge issue/drupal-3238915:3238915-refactor-if-feasible into 9.3.x
1 file
+ 18
6
Compare changes
  • Side-by-side
  • Inline
  • 9aade7f4
    Issue #2842141 by hchonov: Document that more specific hooks might be called... · 9aade7f4
    Alex Pott authored
    Issue #2842141 by hchonov: Document that more specific hooks might be called before the primary hook depending on the module names
@@ -225,9 +225,15 @@ function hook_form_alter(&$form, \Drupal\Core\Form\FormStateInterface $form_stat
@@ -225,9 +225,15 @@ function hook_form_alter(&$form, \Drupal\Core\Form\FormStateInterface $form_stat
* rather than implementing hook_form_alter() and checking the form ID, or
* rather than implementing hook_form_alter() and checking the form ID, or
* using long switch statements to alter multiple forms.
* using long switch statements to alter multiple forms.
*
*
* Form alter hooks are called in the following order: hook_form_alter(),
* The call order is as follows: all existing form alter functions are called
* hook_form_BASE_FORM_ID_alter(), hook_form_FORM_ID_alter(). See
* for module A, then all for module B, etc., followed by all for any base
* hook_form_alter() for more details.
* theme(s), and finally for the theme itself. The module order is determined
 
* by system weight, then by module name.
 
*
 
* Within each module, form alter hooks are called in the following order:
 
* first, hook_form_alter(); second, hook_form_BASE_FORM_ID_alter(); third,
 
* hook_form_FORM_ID_alter(). So, for each module, the more general hooks are
 
* called first followed by the more specific.
*
*
* @param $form
* @param $form
* Nested array of form elements that comprise the form.
* Nested array of form elements that comprise the form.
@@ -277,9 +283,15 @@ function hook_form_FORM_ID_alter(&$form, \Drupal\Core\Form\FormStateInterface $f
@@ -277,9 +283,15 @@ function hook_form_FORM_ID_alter(&$form, \Drupal\Core\Form\FormStateInterface $f
* one exists) check the $form_state. The base form ID is stored under
* one exists) check the $form_state. The base form ID is stored under
* $form_state->getBuildInfo()['base_form_id'].
* $form_state->getBuildInfo()['base_form_id'].
*
*
* Form alter hooks are called in the following order: hook_form_alter(),
* The call order is as follows: all existing form alter functions are called
* hook_form_BASE_FORM_ID_alter(), hook_form_FORM_ID_alter(). See
* for module A, then all for module B, etc., followed by all for any base
* hook_form_alter() for more details.
* theme(s), and finally for the theme itself. The module order is determined
 
* by system weight, then by module name.
 
*
 
* Within each module, form alter hooks are called in the following order:
 
* first, hook_form_alter(); second, hook_form_BASE_FORM_ID_alter(); third,
 
* hook_form_FORM_ID_alter(). So, for each module, the more general hooks are
 
* called first followed by the more specific.
*
*
* @param $form
* @param $form
* Nested array of form elements that comprise the form.
* Nested array of form elements that comprise the form.
Loading