It is very common to use exposer filters along with the views. By default, Drupal doesn't provide any option to sort out the values shown to a user in an exposed form filter. To overcome this, enable Better Exposed filters  and then you will get an option to sort the options shown in the exposed filter.

Whenever working on a multilingual website you must have noticed that views by default start showing all the translations of available nodes in separate rows. This might be a required behaviour sometimes but most of the time it is very confusing for the users and feels like content duplicacy. This can easily be solved by setting 2 additional settings in the views:

1. Add Filter -> Respective Entity (Translation Language) = Content Language Selected for the Page.

2. Rendering Language = Content Language Selected for the Page.

In case you are using relationships as well in the view (and related entities are marked translatable as well), you might have to set a translation language filter for all the entities. Feel free to set different values for these 2 options to achieve the required behaviour.       

Many times, we add a hook_update_n to change schema, perform relevant options for new release etc. Sometimes running this function manually is required to debug it's working or re run the logic which may not have been implemented because of failed updates. You can use Drush to run any particular function in this way:

drush php-eval "module_load_include('install', 'YOUR_CUSTOM_MODULE', 'YOUR_CUSTOM_MODULE'); YOUR_CUSTOM_MODULE_update_8001();"

You can configure token in this way to achieve this:

[node:source:title]
or
[node:source:field_example]

This will ensure that token will return title or field_example only in the original language in which they were created.

In case you are wondering how you can update Lando in your local system, here are easy steps to do the same:

1. Go to https://github.com/lando/lando/releases/ and check if there is any new release.

2. Go under the assets column and try to find the download link of the .deb release type. Eg: https://github.com/lando/lando/releases/download/v3.1.0/lando-v3.1.0.deb

3. Open the terminal and go to the 'Downloads' directory. (cd ~/Downloads).

4. Enter wget https://github.com/lando/lando/releases/download/v3.1.0/lando-v3.1.0.deb (The link you got from the release section.)

5. Enter sudo dpkg -i lando-v3.1.0.deb (The downloaded file is passed as a parameter to the command).

6. Verify the Lando version in local by entering the command lando version.

You can use the following snippet to load multiple nodes without getting timeout or memory-related issues.

use Drupal\node\Entity\Node; 
$nids = \Drupal::entityQuery('node')->condition('type', 'YOUR_CONTENT_TYPE')->execute();
$nodes = Node::loadMultiple($nids);
foreach ($nodes as $node) {  
  // Perform field-related operations.
  $field_value = $node->field_machine_name->getValue()[0]
}

You can use the following code snippet to change the required attribute of the path field in the node form alter in this way:

/**
 * Implements hook_form_FORMID_alter().
 */
function example_module_form_node_form_alter(&$form, &$form_state) {
  $form['path']['widget'][0]['#open'] = TRUE;
  $form['path']['widget'][0]['alias']['#required'] = TRUE;

}

This will keep the path tab open by default and mark the alias field as required.

You can use the following code to set URL alias for a node if your website also uses Pathauto

 $node->path = [

      'alias' => '/' . $node_url,
      'pathauto' => Drupal\pathauto\PathautoState::SKIP,

];
    $node->save();

Where $node_url is the desired alias and $node is loaded node object.

Custom REST Resource can be get used in case you are trying to expose some data from your Drupal website to another external system. In the REST resource code, you might have to access any Drupal services to generate the desired output. Here is a sample code to achieve that.

<?php

namespace Drupal\example\Plugin\rest\resource;

use Drupal\Core\Config\Config;
use Drupal\Core\Entity\EntityTypeManagerInterface;
use Drupal\Core\Session\AccountProxyInterface;
use Drupal\node\Entity\Node;
use Drupal\rest\ModifiedResourceResponse;
use Drupal\rest\Plugin\ResourceBase;
use Drupal\rest\ResourceResponse;
use Psr\Log\LoggerInterface;
use Symfony\Component\DependencyInjection\ContainerInterface;
use Symfony\Component\HttpKernel\Exception\AccessDeniedHttpException;

/**
 * An example REST resource to expose data from Drupal.
 *
 * @RestResource(
 *   id = "example_resource",
 *   label = @Translation("Example Resource"),
 *   uri_paths = {
 *     "canonical" = "/example-resource-path"
 *   }
 * )
 */
class ExampleRestResource extends ResourceBase {
  
  /**
   * Drupal\Core\Entity\EntityTypeManagerInterface definition.
   *
   * @var \Drupal\Core\Entity\EntityTypeManagerInterface
   */
  protected $entityTypeManager;

  /**
   * Drupal configuration instance.
   *
   * @var \Drupal\Core\Config\Config
   */
  protected $apiKeyConfig;
  
  /**
   * A current user instance.
   *
   * @var \Drupal\Core\Session\AccountProxyInterface
   */
  protected $currentUser;

  /**
   * Constructs a ExampleResource instance.
   *
   * @param array $configuration
   *   A configuration array containing information about the plugin instance.
   * @param string $plugin_id
   *   The plugin_id for the plugin instance.
   * @param mixed $plugin_definition
   *   The plugin implementation definition.
   * @param array $serializer_formats
   *   The available serialization formats.
   * @param \Psr\Log\LoggerInterface $logger
   *   A logger instance.
   * @param \Drupal\Core\Entity\EntityTypeManagerInterface $entity_type_manager
   *   The entity type manager.
   * @param \Drupal\Core\Config\Config $api_key_config
   *   The configuration file.
   * @param \Drupal\Core\Session\AccountInterface $current_user
   *   The currently authenticated user.
   */
  public function __construct(
    array $configuration,
    $plugin_id,
    $plugin_definition,
    array $serializer_formats,
    LoggerInterface $logger,
    AccountProxyInterface $current_user,
    EntityTypeManagerInterface $entity_type_manager,
    Config $api_key_config
  ) {
    parent::__construct($configuration, $plugin_id, $plugin_definition, $serializer_formats, $logger);
    $this->currentUser = $current_user;
    $this->entityTypeManager = $entity_type_manager;
    $this->apiKeyConfig = $api_key_config;
  }

  /**
   * {@inheritdoc}
   */
  public static function create(ContainerInterface $container, array $configuration, $plugin_id, $plugin_definition) {
   return new static(
      $configuration,
      $plugin_id,
      $plugin_definition,
      $container->getParameter('serializer.formats'),
      $container->get('logger.factory')->get('example'),
      $container->get('current_user'),
      $container->get('entity.manager'),
      $container->get('config.factory')->get('example.settings')
   );
  }

  /**
   * Responds to GET requests.
   *
   *
   * @return \Drupal\rest\ResourceResponse
   *   The HTTP response object.
   *
   * @throws \Symfony\Component\HttpKernel\Exception\HttpException
   *   Throws exception expected.
   */
  public function get() {
    //Access the entity type manager and config service in this way.
    $this->entityTypeManager;
    $this->apiKeyConfig->get('example_setting_key');
    //Rest of the code to follow.
  }

}
 

Whenever we send a request to Drupal website from our embedded JS application, we have to send a CSRF token with request otherwise it is seen as request forgery issue. You can provide CSRF token to your JS application in the following way:

/**
 * Implements hook_page_attachments().
 */
function example_module_page_attachments(array &$attachments) {
  $attachments['#attached'] = [
    'drupalSettings' => [
      'csrf' => \Drupal::csrfToken()->get(CsrfRequestHeaderAccessCheck::TOKEN_KEY),
    ],
  ];
}

And in your JS application CSRF token can be accessed from drupalSettings object. Make sure this token is added to every request to avoid X-CSRF token not found issues.