Add @interactors/cli

[wKich]

Motivation

First step towards to bigtest v2. Changes to generate environmental agent.ts with desired interactors

Approach

Changed initialisation for matchers through using createMatcher and added abstract classes for matchers and interactors to correctly identify defined them
Added @interactors/cli with ability to generate agent.ts

TODOs and Open Questions

• Missing ok and err function from manually written agent.ts

[changeset-bot]

🦋 Changeset detected

Latest commit: c67dbfa

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 4 packages

Name	Type
@interactors/core	Minor
@interactors/keyboard	Patch
@interactors/html	Patch
@interactors/material-ui	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[netlify]

✅ Deploy Preview for interactors canceled.

Name	Link
🔨 Latest commit	c67dbfa
🔍 Latest deploy log	https://app.netlify.com/sites/interactors/deploys/6697a280ed534b000824dfbe

[taras]

🔥 I'll leave it to @cowboyd to do the review but this is exciting

[cowboyd]

@wKich This is looking awesome!!!

I'm thinking that we should perhaps make only a single global property on the globalThis object. This means that among other things we're concentrated on a single place, and also, we can make a nice TypeScript interface for it. What about:

interface InteractorAgent {
  run(interaction: Interaction): Result<void>;
  interactors: Record<string, InteractorConstructor>;
  matchers: Record<string, MatcherConstructor>;
};

The other thing I'm thinking is that the rematch() function is a little too clever. We should make every value that is processes be boxed into a type that is reified by the agent. This will mean that rematch can be made into a generic construct() that construct anything.

The next step is that we need to generate the constructors that will be used on the client side to send the data over to the agent.

[cowboyd]

I've opened a ticket #265 to have a more complete picture of what the CLI should accomplish. Let's start with the build command and we can go from there.

[cowboyd]

I tried to use it today and was almost successful, but not quite.

• For simplicity's sake, Let's get rid of interactors.config.js for now and say that everything has to be specified on the command line via arguments and options.
• The directory loading using dynamic import() will load relative to the module that is calling it, so we can't use relative paths. Instead, we want to import relative to the directory from which the CLI was invoked, so we should import absolute paths that are resolved relative to process.cwd()
• The opposite is true of the agent.template.ts. It is being read relative to process.cwd(), but we need to copy the agent template to the dist directory as part of the build and read it relative to the interactors cli sources.

[cowboyd]

Suggested change

	import { matcherDescription } from './matcher';
	import { MaybeMatcher } from '../dist';
	import { MaybeMatcher, matcherDescription } from './matcher';

[cowboyd]

This was causing the build to fail. Looks like maybe VSCode was importing this automatically.