andrewlinfoot

const toArray = a => (Array.isArray(a) ? a : [a]);

export async function waitForXpath(page, selector, options = {}) {
  return page.waitForFunction(
    selector => {
      return (
        null !==
        document.evaluate(
          selector,
          document,

slightfoot

///
/// Flutter Captured Error Reporting
/// Created by Simon Lightfoot
/// 
/// Copyright (C) DevAngels Limited 2018
/// License: APACHE 2.0 - https://www.apache.org/licenses/LICENSE-2.0
///
import 'dart:async';
import 'dart:io';
import 'dart:ui' as ui show window;

slightfoot

import 'package:flutter/cupertino.dart';
import 'package:flutter/foundation.dart';
import 'package:flutter/material.dart';


void main() {
	//runApp(IOSApp());
	//runApp(AndroidApp());
	runApp(defaultTargetPlatform == TargetPlatform.iOS ? IOSApp() : AndroidApp());
}

jeroen-meijer

#!/bin/sh

# To run, download the script or copy the code to a '.sh' file (for example 'flutterrepair.sh') and run like any other script:
#   sh ./flutterrepair.sh
# or
#   sudo sh flutterrepair.sh

echo "Flutter Repair (by jeroen-meijer on GitHubGist)"

echo Cleaning project...

dcolthorp

/** Used by Flavor to mark a type in a readable way. */
export interface Flavoring<FlavorT> {
  _type?: FlavorT;
}
/** Create a "flavored" version of a type. TypeScript will disallow mixing flavors, but will allow unflavored values of that type to be passed in where a flavored version is expected. This is a less restrictive form of branding. */
export type Flavor<T, FlavorT> = T & Flavoring<FlavorT>;

/** Used by Brand to mark a type in a readable way. */
export interface Branding<BrandT> {
  _type: BrandT;

JoeyBurzynski

58 bytes of CSS to look great nearly everywhere

When making this website, i wanted a simple, reasonable way to make it look good on most displays. Not counting any minimization techniques, the following 58 bytes worked well for me:

main {
  max-width: 38rem;
  padding: 2rem;
  margin: auto;
}

martinheld

GraphQL introspection query via curl

cat introspection_query.json

{ 
  "query": "query IntrospectionQuery {
      __schema {
        queryType { name }
        mutationType { name }

reggi

I am trying to find a way that a resolver can essentially return another resolver using [nest.js][1] for creating [Resolvers][2], and [type-graphql][3] to create [object types][4].

Here's an example with the star-wars graphql api

{
  allVehicles(first: 1, last: 100) {
    vehicles {
      name

bodokaiser

import React from "react"
import { CognitoUser } from "@aws-amplify/auth"

import { useAuth } from "./hooks"
import { SignInInput } from "./types"

interface AuthState {
  user: CognitoUser | null
  signIn(input : SignInInput): Promise<void>
  signOut(): Promise<void>

kennovation1

# busmon.py
# Monitor CloudWatch Logs for EventBridge traffic.
#
# This script assumes that there is a Lambda function snooping an EventBridge bus
# and logging the events to a CloudWatch Logs group.
#
# Your format will likely be different and will require slight adjustments to the parsing
# logic below. The default format assumed for this version is:
# timestamp and other stuff|field|field|field|SNOOPED detail-type: <eventName> jsonString
# That is 5 pipe-delimited fields, where the last field is the only field used.