AlexandrHoroshih

test('stuff', async () => {
  // форкаем домен, создаем новый независимый скоуп
  const scope = fork(root, { 
    // в конфиге форка будут модификации, которые применятся к скоупу
    values: new Map()
                 .set($myStore, value), // подменили стартовое значение стора эксклюзивно для этого скоупа
    handlers: new Map()
                   .set(myFx, mockHandler) // подменили хэндлер эффекта эксклюзивно для этого скоупа
  });
 

AlexandrHoroshih

<div block>
  <div>
    <div block>
      <div>
        <div block>
          <div>
            <div>
              <div block>
                <div>
                  <div block>

AlexandrHoroshih

import { matchPath, RouteProps } from "react-router";

// historyUpdated event is subscribed to history via history.listen or any other way

export const createPathMatcher = <Match = unknown>(config: {
  path: string | string[] | RouteProps;
  clock?: Event<any> | Store<any> | Effect<any, any>;
}) => {
  return sample({
    source: historyUpdated,

AlexandrHoroshih

import singletonRouter from 'next/router';
import type { NextRouter } from 'next/router';
// import { createDomain } from 'effector';

import { root } from '../../src/core/root';

export const routerDomain = root.createDomain('router');

type NextRouterEventWithError = [any, string];

AlexandrHoroshih

// an option to create bindings to history
// usage is like
//
// export const historyUpdated = createEvent<HistoryUpdate>();
// export const clocks = createHistoryClocks();
//
// clocks have fields like `push, replace, go` and so on
// can be used like clocks.push({ to: "path" })
//
// wrapHistory({

AlexandrHoroshih

test('stuff', async () => {
  // create new forked scope, which is completly independent
  const scope = fork({ 
    // apply modifications like initial store values in this scope
    values: new Map()
                 .set($myStore, "value"), // changed value in $myStore specifically for this scope
    handlers: new Map()
                   .set(myFx, mockHandler) // changed effect handler to mock one for this scope
  });
 

AlexandrHoroshih

console.log(context)

return {
 type: "stuff",
 context,
}

AlexandrHoroshih

 // rules are the same as for react hooks, order must not change
  const [last, setLast] = game.useStash(0);
  const next = (last + 1) < game.myBots.length ? last + 1 : 0;
  setLast(next)
  const current = game.myBots[last];


  for (let i = 0; i < game.myBots.length; i++) {
    const my = game.myBots[i];
    const target = game.lib.findClosest(my, game.enemyBots);

AlexandrHoroshih

As for now, every unit in effector must have an unique stable identifier and factories of units must be marked at effector/babel-plugin settings in a special way by adding path to factory definiton to factories list, so every group of units created from factory call have ther own sids and other metadata.

As it turns out, this way can be really confusing for many developers and, while it fairly easy to use with external libs like patronum or @effector/reflect, this maybe hard to notice if something went wrong when dealing with project-specific custom factories

Proposal

AlexandrHoroshih

const currentEnv = process.env.NODE_ENV || "prettier";
const withLogger = process.env.LOGGER === "true";

const babelPluginOverrides = {
  prettier: {
    presets: [
      "@babel/preset-env",
      "@babel/preset-react",
      "@babel/preset-typescript",
    ],