oksana-c

<?php

use Drupal\DrupalExtension\Context\DrupalContext,
    Drupal\DrupalExtension\Event\EntityEvent,
    Drupal\Component\Utility\Random;

use Behat\Behat\Context\BehatContext,
    Behat\Behat\Context\Step,
    Behat\Behat\Context\Step\Given,
    Behat\Gherkin\Node\PyStringNode,

oksana-c

l(
  t('<span></span>Link Title'), 
  'link_path', 
  array(
    'attributes' => array(
      'class' => array('menu-link'), 
      'id' =>'faq-page',
    ), 
    'html' => TRUE,
  ),

oksana-c

<?php
/**
 * Create media entities from existing file fields.
 *
 * @link https://chromatichq.com/blog/migrating-drupal-file-fields-media-entities-without-migrate-module
 */
function MODULENAME_update_8001() {
  // Nodes types that will get media migrated.
  $node_types = ['article','event','page','session','sponsor'];
  // Map old file fields => new media fields.

oksana-c

drush eval "var_dump(Drupal\Component\Utility\Crypt::randomBytesBase64(55))"

oksana-c

<?php
use Drupal\node\Entity\Node;

/**
 * Before attaching a term(s) to a term reference field,
 * Must know:
 *   - field_example_name: the full name of the term reference field
 *   - tid: the term ID(s) to attach
 *
 * Keep in mind that this example uses Node::load() 

oksana-c

<?php 
/**
 * Implements hook_inline_entity_form_table_fields_alter().
 *
 * Displays a field from a custom entity in the Inline Entity Form windget table. 
 */
function MODULENAME_inline_entity_form_table_fields_alter(&$fields, $context) {
  // Display Entity field in a column within Inline Entity Form widget.
  if ($context['parent_bundle'] == 'content_type_parent_to_ief' && $context['field_name'] == 'entity_reference_field_name') {
    // Unset original IEF label if needed.

oksana-c

<?php

namespace Drupal\my_module\Services;

use Drupal\Core\Config\ConfigFactory;

/**
 * Class MyService.
 *
 * @package Drupal\my_module\Services

oksana-c

contents of the theme/preprocess/README.md

Defining preprocess hooks

Rather than placing your preprocess hooks directly in the .theme file you can manage them in automatically discovered and lazy-loaded include files. It is even possible to organize them in sub-folders. This feature greatly improves the maintainability of large themes that would otherwise contain hundreds of lines of unrelated code in your template.php file.

oksana-c

<?php

/**
 * Implements hook_search_api_solr_converted_query_alter().
 *
 * Modifies Solarium query to group results by field.
 * Modifies Solarium query to sort results by first geofield value within the multivalue field.
 */
function MODULE_search_api_solr_converted_query_alter(\Solarium\Core\Query\QueryInterface $solarium_query, \Drupal\search_api\Query\QueryInterface $query) {
  // Alter the Solarium query.

oksana-c

<?php

// Import arbitrary config from a variable.
$config = \Drupal::service('config.factory')->getEditable('filter.format.basic_html');
$config->setData($data)->save();

// Or, re-import the default config for a module or profile, etc.
\Drupal::service('config.installer')->installDefaultConfig('module', 'my_custom_module');

// Or, import YAML config an arbitrary directory.