Ifmr24

import React, { useState, useEffect } from 'react';

export default () => {
    // Definimos los estados
    const [name, setName] = useState(String)
    const [count, setCount] = useState(Number)

    // Los estados definidos se pueden usar dentro de otras funciones
    function obtenerName(){
        console.log(name)

daliborgogic

<?php
  function pwa_preview_link() {
      $slug = basename(get_permalink());
      $pwadomain = 'https:/example.com';
      $pwadir = '/';
      $pwaurl = "$pwadomain$pwadir$slug";
      return "$pwaurl";
  }
  add_filter('preview_post_link', 'pwa_preview_link');

itsdavidmorgan

/************************************************
  Audio Blocks
************************************************/

.wp-block-audio {
	margin-left: 0px;
	margin-right: 0px;
}
.wp-block-audio audio {
	width: 100%;

getify

"use strict";

[foo,bar] = TNG(foo,bar);
// NOTE: intentionally not TNG(..) wrapping useBaz(), so that it's
// basically like a "custom hook" that can be called only from other
// TNG-wrapped functions

function foo(origX,origY) {
   var [x,setX] = useState(origX);
   var [y,setY] = useState(origY);

bvaughn

This API was removed in React 17

---

Interaction tracing with React

React recently introduced an experimental profiler API. After discussing this API with several teams at Facebook, one common piece of feedback was that the performance information would be more useful if it could be associated with the events that caused the application to render (e.g. button click, XHR response). Tracing these events (or "interactions") would enable more powerful tooling to be built around the timing information, capable of answering questions like "What caused this really slow commit?" or "How long does it typically take for this interaction to update the DOM?".

With version 16.4.3, React added experimental support for this tracing by way of a new NPM package, scheduler. However the public API for this package is not yet finalized and will likely change with upcoming minor releases, so it should be used with caution.

RStankov

class LoadMoreButton extends React.Component {
  render() {
    const { data, path, children, ...otherProps } = this.props; 
 
    return (
      <button {...otherProps} onClick={this.onClick}>
        {children || 'Load more'}
      </button>
    );
  }

courtneymyers

<?php

/*
 * -----------------------------------------------------------------------------
 * Advanced Custom Fields Modifications
 * -----------------------------------------------------------------------------
*/
function PREFIX_apply_acf_modifications() {
?>
  <style>

DrPaulBrewer

// upload.js, from https://github.com/googledrive/cors-upload-sample
// Contributors Steve Bazyl, Mike Procopio, Jeffrey Posnick, Renaud Sauvain
// License: Apache 2.0 http://www.apache.org/licenses/LICENSE-2.0
//
// Implements Resumable Upload for Google Drive as described by
// https://developers.google.com/drive/v3/web/resumable-upload
//
// Modified by Paul Brewer, Economic and Financial Technology Consulting LLC
// Nov. 1 2017
//  1. use Google Drive API V3 instead of V2

tristen

class Map extends React.Component {
  componentDidMount() {
    this.map = new mapboxgl.Map({
      container: this.mapContainer,
      style: 'mapbox://styles/mapbox/streets-v9'
    });
  }

  componentWillUnmount() {
    this.map.remove();

tristen

import Modal from 'some-react-modal'

export class CoolModal extends React.Component {
  render() {
    const { title, size, onExit, children } = this.props;
    const width = size === 'small' ? '360px' : '600px';
    <Modal
      onExit={onExit}
      enableKeys={true}
      closeOnOutsideClick={true}>