adamsoffer

import {
  Player,
  LivepeerConfig,
  createReactClient,
  studioProvider,
} from "@livepeer/react";

const client = createReactClient({
  provider: studioProvider({ apiKey: "e2475873-a877-4c48-97bb-738677a94b89" }),
});

adamsoffer

"""
Represents a delegator's pool share
"""
type Share @entity {
  "Unique identifer for the share (formed using the delegator's address and round number)"
  id: ID!
  "The delegator's share of reward tokens"
  rewardTokens: BigInt
  "The delegator's share of fees"
  fees: BigInt

adamsoffer

Keybase proof

I hereby claim:

• I am adamsoffer on github.
• I am adamsoffer (https://keybase.io/adamsoffer) on keybase.
• I have a public key ASDJ9qQsgkbd6Q3NgNWeqCgZq1Agd8g_8nWTM51sDvoXDgo

To claim this, I am signing this object:

adamsoffer

export const getComponent = component => {
  const componentName = pascalCase(component.type)
  const Component = require(`../components/${componentName}`).default
  return (
    <Component
      key={component.type}
      primary={component.primary}
      fields={component.fields}
    />
  )

adamsoffer

0xe4130d072FA1a4BdBf5051a6e0764e77a4aA6370

adamsoffer

0x920c283fde4173486b77560b4bf86140a291f458

adamsoffer

LESS Coding Guidelines

Medium uses a strict subset of LESS for style generation. This subset includes variables and mixins, but nothing else (no nesting, etc.).

Medium's naming conventions are adapted from the work being done in the SUIT CSS framework. Which is to say, it relies on structured class names and meaningful hyphens (i.e., not using hyphens merely to separate words). This is to help work around the current limits of applying CSS to the DOM (i.e., the lack of style encapsulation) and to better communicate the relationships between classes.

Table of contents

• JavaScript