mergebandit

// Available variables:
// - Machine
// - interpret
// - assign
// - send
// - sendParent
// - spawn
// - raise
// - actions
// - XState (all XState exports)

mergebandit

  // Available variables:
  // - Machine
  // - interpret
  // - assign
  // - send
  // - sendParent
  // - spawn
  // - raise
  // - actions

mergebandit

I recently came across a Dockerfile that was taking 23 minutes to build that looked something like the following:

... setup

mkdir app
WORKDIR app

RUN npm config set registry "<some npm registry url>"
RUN npm config set some_other_key ""

mergebandit

Mocking Services

When mocking services in jest, given:

const someMethodMock = mockService.someMethod as jest.Mock;
beforeEach(() => {
  jest.clearAllMocks()
})

mergebandit

  // Available variables:
  // - Machine
  // - interpret
  // - assign
  // - send
  // - sendParent
  // - spawn
  // - raise
  // - actions

mergebandit

React Router

TIL - under the hood RR uses React.createElement for any inline functions passed to ...} />. If you don't want your component to fully remount, use ... } /> instead.

mergebandit

  // Available variables:
  // - Machine
  // - interpret
  // - assign
  // - send
  // - sendParent
  // - spawn
  // - raise
  // - actions

mergebandit

const service = {
  addMfa: mfaOpt => {
    console.log("service call: addMfa", mfaOpt);
    return Promise.resolve(mfaOpt);
  },
  deleteMfa: mfaOpt => {
    console.log("service call: deleteMfa", mfaOpt);
    return Promise.resolve(mfaOpt.mfaId);
  },
  verifyMfa: mfaOpt => {

mergebandit

/*
  We now have a fully baked delete example where we update context
*/
const service = {
  addMfa: (mfaOpt) => Promise.resolve(mfaOpt),
  deleteMfa: (mfaOpt) => Promise.resolve(mfaOpt.id)
}

const notificationMachine = Machine({
  id: 'notification',

mergebandit

  // Available variables:
  // - Machine
  // - interpret
  // - assign
  // - send
  // - sendParent
  // - spawn
  // - raise
  // - actions