This setup uses some tricks to ensure that the right email/name/ssh-key is used for the right repos without having to think about it ever again.
~/.ssh/id_ed25519 and ~/.ssh/id_ed25519_work
| // @ts-check | |
| "use strict" | |
| /** | |
| * Set up datadog tracing. This should be called first, so Datadog can hook | |
| * all the other dependencies like `http`. | |
| */ | |
| function setUpDatadogTracing() { | |
| const { tracer: Tracer } = require('dd-trace') | |
| const tracer = Tracer.init({ |
This document isn't an explainer on Feature Flags, you can find that with my amateur writeup, or literally hundreds of better writeups out there.
This document is also agnostic to the choice of service you'd use: LaunchDarkly or split.io or optimizely or whatever; that's orthogonal to this conversation.
Instead, this document is a list of considerations for implementing a client for using Feature Flags for User Interface development. Service providers usually give a simple fetch and use client and that's it; I contend that there's a lot more to care about. Let's dive in.
To encourage usage, we'd like for the developer experience to be as brutally simple as possible. So, this should be valid usage:
| import * as React from 'react'; | |
| import { theme } from './theme'; | |
| import { ThemeProvider, createGlobalStyle } from './styled-components'; | |
| const GlobalStyle = createGlobalStyle` | |
| body { | |
| font-family: Times New Roman; | |
| } | |
| `; |
I made a little styling lib called glam
(some features are in development)
let's start off with the simplest use case. we'll make an 'index.html' page,
and assume we've setup our js bundler to output bundle.js