Actions in nested machines

[Santiago-j-s]

I think that i found a bug in lucy 0.3.4

use './utils.js' {assignDays}

machine testMachine {
  action assignDays = assignDays

  initial state test {}
}

compiles to

import { createMachine } from 'xstate';
import { assignDays } from './utils.js';

export function createTestMachine({ context = {} } = {}) {
  return createMachine({
    initial: 'test',
    context,
    states: {
      test: {

      }
    }
  }, {
    actions: {
      assignDays: assignDays
    }
  });
}

which is ok, but

use './utils.js' {assignDays}

machine testMachine {
  action assignDays = assignDays

  initial state test {
    machine nested {
    }
  }
}

compiles to

import { createMachine } from 'xstate';
import { assignDays } from './utils.js';

export function createTestMachine({ context = {} } = {}) {
  return createMachine({
    initial: 'test',
    context,
    states: {
      test: {
        context
      }
    }
  });
}

where actions dissapeared

[matthewp]

Thanks for filing! Why do you expect it to be included in the second where it's not used?

[Santiago-j-s]

Sorry, I didn't express myself well. I expect it to be included only if it's used, a better test case would be

use './utils.js' {assignDays}

machine testMachine {
  action assignDays = assign(days, assignDays)
  
  initial state initial {
    click => assignDays => newState
  }

  final state newState {}
}

machine testNestedMachine {
  initial state test {
    machine nested {
      action assignDays = assign(days, assignDays)

      initial state initial {
        click => assignDays => newState
      }

      final state newState {}
    }
  }
}