simonrelet

import React from 'react'

/**
 * @typedef {object} State The state of asynchronous hooks.
 * @property {object | null} error The error.
 * @property {boolean} pending Whether the call is pending.
 * @property {any | null} result The result of the asynchronous call.
 */

/** @type {State} */

hubgit

import { FieldProps } from 'formik'
import React from 'react'
import Select, { Option, ReactSelectProps } from 'react-select'

export const SelectField: React.SFC<ReactSelectProps & FieldProps> = ({
  options,
  field,
  form,
}) => (
  <Select

cheungnj

# Adapted from https://tinyapps.org/blog/nix/201701240700_convert_asciidoc_to_markdown.html
# Using asciidoctor 1.5.6.1 and pandoc 2.0.0.1
# Install pandoc and asciidoctor

$ sudo apt install asciidoctor
$ sudo wget https://github.com/jgm/pandoc/releases/download/2.0.0.1/pandoc-2.0.0.1-1-amd64.deb
$ sudo dpkg -i pandoc-2.0.0.1-1-amd64.deb

# Convert asciidoc to docbook using asciidoctor

kahboom

{
  "apiEndpoint": "https://ipaas-staging.b6ff.rh-idev.openshiftapps.com/api/v1",
  "title": "Syndesis",
  "datamapper": {
    "baseJavaServiceUrl": "https://ipaas-staging.b6ff.rh-idev.openshiftapps.com/v2/atlas/java/",
    "baseMappingServiceUrl": "https://ipaas-staging.b6ff.rh-idev.openshiftapps.com/v2/atlas/"
  },
  "oauth": {
    "clientId": "ipaas-ui",
    "scopes": [],

bleathem

PatternFly Web Components / Framework-Native Proposal

Where we stand

The PatternFly roadmap outlines a proposal to scale framework support by adopting a Web Component based solution for implementing pattern behaviours to support multiple web frameworks.

By building prototypes for PatternFly-webcomponents, we have shown that framework integration of web components is possible, but benefits from the introduction of framework-specific shims to provide application developers with a framework-native experience when consuming the web components.

The problem

Front-end developers are by-and-large in favor of the web component approach for implementing pattern behaviours. However, we need to achieve a critical mass of pattern implementations in order for developers to adopt the solution and begin contributing back their own implementations.

gashcrumb

ipaas-edit-connector-options page 3:

{
  "messages": [
    
  ],
  "valid": true,
  "canExecute": true,
  "out": "",
  "err": "",

gashcrumb

    getAll(): Observable<Connection[]> {
				return this.forge.executeCommand({
					commandId: 'ipaas-search-connectors',
					data: {
						inputList: [{ latest: true, filter: '' }]
					}
				})
				.map((body) => {
					return JSON.parse(body.message);
				})

msmfsd

// Async/Await requirements: Latest Chrome/FF browser or Babel: https://babeljs.io/docs/plugins/transform-async-to-generator/
// Fetch requirements: Latest Chrome/FF browser or Github fetch polyfill: https://github.com/github/fetch

// async function
async function fetchAsync () {
  // await response of fetch call
  let response = await fetch('https://api.github.com');
  // only proceed once promise is resolved
  let data = await response.json();
  // only proceed once second promise is resolved

gashcrumb

brew update
brew upgrade
brew install --HEAD xhyve

# requires installing golang, 'brew install golang', set 'GOPATH' in your .bashrc to some directory like ~/go
go get github.com/docker/machine
cd $GOPATH/src/github.com/docker/machine
make build && make install
brew install docker-machine-driver-xhyve

paulirish

What forces layout / reflow

All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.

Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.

Element APIs

Getting box metrics

• elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent