codfish

import React from 'react';
import PropTypes from 'prop-types';
import clsx from 'clsx';
import styles from './Module.style';
import { Provider } from '../context/module';

const Module = ({ expandable, closed, children, className: classNameProp, ...other }) => {
  const className = clsx(styles.root, classNameProp);

  return (

codfish

import { RSAA } from 'redux-api-middleware';
import get from 'lodash/get';

/**
 * Intercept redux api middleware actions and bailout of api resource requests
 * if the resource is already in the store.
 *
 * NOTE: State always gets updated on non-GET requests, essentially updating our "cache"
 *
 * Examples of resource routes that we want to cache:

codfish

const NUMERALS = {
  I: 1,
  V: 5,
  X: 10,
  L: 50,
  C: 100,
  D: 500,
  M: 1000,
  IV: 4,
  IX: 9,

codfish

xcode-select --install
ssh-keygen
cat ~/.ssh/id_rsa.pub | pbcopy
# -> add ssh key to github

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/codfish/dotfiles/main/install.sh) --with-apps"

# -> open dropbox and log in
sh ~/Dropbox/configfiles/bin/setup

codfish

// ***********************************************************************************
// meta-service.js

'use strict';

/**
 * Meta Service
 *
 * The Meta Service allows you to abstract a lot of business logic
 * that goes into setting meta & link tags for your templates.

codfish

{
  "version": 2,
  "name": "codfish.io",
  "alias": "codfish.io",
  "builds": [{ "src": "package.json", "use": "@now/static-build" }],
  "routes": [
    {
      "src": ".*\\.(js|css|jpg|jpeg|gif|png|svg|txt|ttf|woff2|webmanifest)$",
      "headers": {
        "Cache-Control": "public, max-age=157680000, s-maxage=157680000"

codfish

My personal & professional linting setup. Run's Prettier as an ESLint rule via their ESLint plugin. Dynamic support for react or non-react applications depending on your project dependencies. Dynamic inclusion of Kent C Dodds' ESLint Jest config depending on your project dependencies.

Convenient opt-in configs for projects using Docker or Ethereum to avoid common false positives.

To understand more, see https://github.com/codfish/eslint-config-codfish.

To avoid having to manually setup everything and add all configuration/boilerplate code to your project, use cod-scripts instead. It was forked from kcd-scripts and ultimately inspired by react-scripts.

Why

codfish

Documenting Your Code

This is a detailed spec on how developers should be documenting their code. While inline code comments are very important, this specification will be focusing on docblock structure.

Docblocks are required for all class methods & properties/attributes. The reason we have this spec, and the reason that actual language standards exist for docblocks, is so that generators will know how to parse your code & render consumable html documentation.

For this reason, documentation standards follow the existing spec's that are currently community standards at the time of writing, and we should be following them.

• Official PHP Standard: https://github.com/phpDocumentor/fig-standards/blob/master/proposed/phpdoc.md
• Official JS Standard: https://jsdoc.app/

codfish

To install a relatively recent version of Faker you'll need to install from a commit. The maintainer is still active and merging new features, but does not cut new releases.

npm install --save-dev faker@Marak/faker.js#<commit-sha>

I.e. npm install --save-dev faker@Marak/faker.js#d3ce6f1 (latest commit at the time of writing).

codfish

/**
 * Handle application errors.
 *
 * NOTE: 500 status code is returned by default.
 *
 * To properly leverage this middleware, rather than return responses in your routes,
 * simply set a response status in the route and then pass the error object to `next`.
 * This middleware will catch that error and handle it in a consistent way across
 * the entire application. For example:
 *