imoby

[
    {
        "name": "Secondary-Hover",
        "key": "72c308280a63f43cdc90f8008988fc84d5128159",
        "theme": "Asurion",
        "type": "PAINT"
    },
    {
        "name": "Primary-Hover",
        "key": "394f465f42b619ae36e4b494314711f8d7b86c5e",

imoby

import React, { createContext, useMemo, useState } from 'react';
import { Mixpanel } from 'mixpanel-react-native';
import { mixpanelToken } from '../../app.json';

type MixpanelContextType = {
  mixpanel: Mixpanel | undefined;
};

const mixpanelContextDefault: MixpanelContextType | undefined = {
  mixpanel: undefined,

imoby

The Ultimate Git Alias Setup

If you use git on the command-line, you'll eventually find yourself wanting aliases for your most commonly-used commands. It's incredibly useful to be able to explore your repos with only a few keystrokes that eventually get hardcoded into muscle memory.

Some people don't add aliases because they don't want to have to adjust to not having them on a remote server. Personally, I find that having aliases doesn't mean I that forget the underlying commands, and aliases provide such a massive improvement to my workflow that it would be crazy not to have them.

The simplest way to add an alias for a specific git command is to use a standard bash alias.

# .bashrc