ruanbekker

My Elasticsearch cheatsheet with example usage via rest api (still a work-in-progress)

Shortlinks:

• Cluster Health
  • Index Level
  • Shard Level
• Nodes Overview
• Indices Overview
• Cluster Maintenance

jcalz

type IBuilder<T> = {
  [k in keyof T]: (arg: T[k]) => IBuilder<T>
} & { build(): T }

function proxyBuilder<T>(): IBuilder<T> {
  var built: any = {};
  var builder = new Proxy({}, {
    get: function(target, prop, receiver) {
      if (prop === 'build') return () => built;
      return (x: any): any => {

davidfowl

using System;
using System.Collections.Generic;
using System.Linq;
using System.Threading;
using System.Threading.Tasks;
using Microsoft.Extensions.Hosting;

namespace WebApplication24
{
    public abstract class HostedService : IHostedService

brunocassol

package main

// A simple demo implementation of a Redis job queue in Go inspired on http://stackoverflow.com/a/34754632
// You'll need to get redis driver package in terminal with: go get -u gopkg.in/redis.v5
// Once it is running, Redis should look like: http://i.imgur.com/P4XlwlP.png
// Terminal should look like: http://i.imgur.com/AS2IIbP.png
// I have 4 days of Go programming experience, have mercy.

import (
	"fmt"

benfoster

        public static void Execute(ChargeCommand command)
        {
            var pipeline = new PipelineBuilder<ChargeContext>()
                                        .Register(new TimingHandler())
                                        .Register(new LoggingHandler())
                                        .Register(new ValidationHandler(
                                            validationPipeline =>
                                            {
                                                validationPipeline.Register(new AmountValidator(maxAmount: 500));
                                            }

oguzhaneren

{
  "variables": {
    "client_id": "",
    "client_secret": "",
    "subscription_id": "",
    "tenant_id": "",
    "object_id": "",

    "resource_group": "",
    "storage_account": "",

NickCraver

<Query Kind="Program">
  <NuGetReference Prerelease="true">Microsoft.Diagnostics.Runtime</NuGetReference>
  <Namespace>Microsoft.Diagnostics.Runtime</Namespace>
  <Namespace>System</Namespace>
  <Namespace>System.IO</Namespace>
  <Namespace>System.Linq</Namespace>
  <Namespace>System.Text</Namespace>
  <Namespace>Microsoft.Diagnostics.Runtime.Utilities</Namespace>
</Query>

benfoster

using System;
using System.Collections.Generic;
using System.Linq;
using System.Threading.Tasks;

namespace PipelineDemo
{
    // http://www.rantdriven.com/post/2009/09/16/Simple-Pipe-and-Filters-Implementation-in-C-with-Fluent-Interface-Behavior.aspx
    public interface IFilter<TContext>
    {

davidfowl

namespace Analogy
{
    /// <summary>
    /// This example shows that a library that needs access to target .NET Standard 1.3
    /// can only access APIs available in that .NET Standard. Even though similar the APIs exist on .NET 
    /// Framework 4.5, it implements a version of .NET Standard that isn't compatible with the library.
    /// </summary>INetCoreApp10
    class Example1
    {
        public void Net45Application(INetFramework45 platform)

gregoryyoung

f(events) -> state
    match f(state, event) -> state

f(state, command) -> events