JaumeGelabert

"use client";

import {
  Dialog,
  DialogContent,
  DialogTitle,
  DialogTrigger
} from "@/components/ui/dialog";
import useDragDrop from "@/hooks/useDragDrop";
import { cn, formatBytes } from "@/lib/utils";

marentdev

/* eslint-disable */
/* tslint:disable */
/*
 * ---------------------------------------------------------------
 * ## THIS FILE WAS GENERATED VIA SWAGGER-TYPESCRIPT-API        ##
 * ##                                                           ##
 * ## AUTHOR: acacode                                           ##
 * ## SOURCE: https://github.com/acacode/swagger-typescript-api ##
 * ---------------------------------------------------------------
 */

clemensv

Tenant Bridges

This document defines a mechanism to establish multiplexed, platform-level information flow between the tenant scopes of different, multitenant platform-as-a-service (PaaS) or software-as-a-service (SaaS) systems. In particular, this specification introduces the concept of a tenant-bridging “channel” that is established as a communication link between the tenants of two cooperating platforms. While the mechanism defined here is quite simple, the solved problem requires quite a bit of context setting:

What are we solving?

The "cooperating platforms" are commonly from different cloud service vendors and are addressing different customer scenarios. Examples might be enterprise resource planning (ERP) on one side and general-purpose application hosting on the other. A scenario to enable might be for the ERP system to be easily extensible with event-driven serverless functionality hosted on the other platform.

In such a scenario, it will likely be the same customer organization who is a te

isaacabraham

using System;
using System.Threading.Tasks;

namespace ConsoleApp8
{
    class Program
    {
        static async Task<int> DoStuff()
        {
            var x = await System.IO.File.ReadAllTextAsync("Foo");

jhewlett

namespace HttpClient.FSharp

open System
open System.Net.Http

type HttpMethod = 
| Post
| Put
| Delete
| Get

akhansari

// ========= Event Sourcing in a nutshell

(*
    FriendlyName: string
        Aggregate friendly name.

    Initial: 'State
        Initial (empty) state we will start with.

    Decide: 'Command -> 'State -> 'Event list

aspnetde

module App

open Elmish

type State = 
    { CurrentUser: string option }

type Msg = 
    | SignIn of string
    | SignOut

goeh

import groovy.json.JsonSlurper
import groovy.json.JsonOutput

def jsonSlurper = new JsonSlurper()
def secrets = jsonSlurper.parse(new File(args[1] ?: "secrets.json")).clients.inject([:]) { map, c -> map[c.client] = c.secret; map } 

def realm = jsonSlurper.parse(new File(args[0]))

for(client in realm.clients) {
  if(secrets[client.clientId]) {

dev01d

// All you need to do is add a font that has pretty good itlaics support i.e Fira, Operator, etc. and then add these two params to your existing User settings.

{
 "editor.fontFamily": "'Operator Mono', Menlo, Monaco, 'Courier New', monospace",
 "editor.tokenColorCustomizations": {
     "textMateRules": [
      {
        "scope": [
          "comment",
          "keyword.control",

yellowbrickc

Scenario: different business teams building parts of a product, splitted by business domains. We are anly communicate via domain events published to a message bus and sometimes via published links.
As the domain events are the "contracts" between the business domains we want to declare and enforce the schemas of the events. 
Our solution is built in node but the concept could work in any stack.