Heitor Althmann heitoralthmann

The Beginner's Guide to React

Lesson 5: Validate Custom React Component Props with PropTypes

Utilizamos propTypes para tipar as props de um componente e garantir que não vão passar um tipo de dado errado, quebrando a aplicação.

Para fazer a validação de nossas props, o time do React disponibiliza uma biblioteca chamada prop-types que nos fornece uma série de funções úteis para realizar este trabalho:

ComponentName.propTypes = {
 propName: PropTypes.string,

STATE OBJECT

I will be representing the whole state of my application with A SINGLE STATE OBJECT.
This state object is read only. Every time I want to change it, I must dispatch an action.
The STATE is the minimum representation of data in my app.

ACTIONS

The ACTION is the minimum representation describing the change to that data.
Action objects MUST HAVE AT LEAST a type property. We better use strings for this option because it is serialisable.
The only way to change the state tree is by dispatching an action.
An action is a plain javascript object describing in the minimum way, what changed in the application.

	<?php

	/**
	* @file
	*
	* Assuming that you've created a queue using the simple queue handler,
	* that means a subqueue has been created automatically with the same name
	* as the queue.
	* Therefore, to get the (sub)queue items programatically, you can do this:
	*/

	<?php

	use Drupal\migrate\MigrateMessage;
	use Drupal\migrate_tools\MigrateExecutable;

	/**
	* Runs a migration.
	*
	* @param string $migration_name
	* The name of the migration to run.

	<?php

	/**
	* Deletes ghost/broken/missing fields from the file system.
	*
	* I've recently run into a problem where some deleted fields were not
	* completely wiped out from the system.
	* This was causing the following error every time I tried to delete a
	* piece of content:
	*

	<?php

	/**
	* Implements hook_entity_operation().
	*/
	function modulename_entity_operation(\Drupal\Core\Entity\EntityInterface $entity) {
	if(in_array($entity->bundle(), ['article'])) {
	$operations = array();

	$operations['play'] = array(

	<?php

	//
	// ATTENTION!
	// This method of resizing field data TRUNCATES the information present in the field.
	// This is heavily based on the solution available at https://github.com/evolvingweb/custom_field_resize
	// with only a minor tweak to truncate field data before resizing the field, so we don't get an SQL error.
	//

	<?php

	\Drupal::logger('some_channel_name')->warning('<pre><code>' . print_r($responseObj, TRUE) . '</code></pre>');

	# Looping through source field values and creating taxonomy terms for each of them (bundle_key and value_key are both required in this scenario)
	field_name:
	-
	plugin: skip_on_empty
	method: process
	source: 'Source-Field-Name'
	-
	plugin: sub_process
	process:
	target_id:

	<?php

	/**
	* @file
	* Functions to support theming in the THEME_NAME theme.
	*/

	/**
	* Implements hook_preprocess_theme().
	*/