Clarification: canDeactivate & forceDeactivate & autoCleanUp

[mahnunchik]

Hi, I've faced with not working canDeactivate by default. I've fixed it by the following code sample:

const router = createRouter([
  { name: 'messages', path: '/messages' },
  { name: 'messages.create', path: '/create' },
], {
  autoCleanUp: false,
});

router.usePlugin(browserPlugin({
  useHash: true,
  forceDeactivate: false,
}));

const canDeactivate = (router) => {
  return (toState, fromState) => {
    // Some conditions
    return false;
  }
}

router.canDeactivate('messages.create', canDeactivate);

router.start();

There are some related issue:

1. Question: Combine Prevent Navigation + Async Data #175
2. canDeactivate for nested routes #163
3. canDeactivate not working properly #368

Question: what are the use cases of canDeactivate without forceDeactivate: false and autoCleanUp: false options?

[mahnunchik]

Another related question: is it correct way to connect View with canDeactivate handler?

// autoCleanUp: true

// route 'messages.create'
const BlockedView = () => {
  const { router } = useRouteNode('messages.create');

  const [blocked, setBlocked] = useState(false);

  router.canDeactivate('messages.create', (router) => (toState, fromState) => {
    return !blocked;
  });
  return (
    <View>
      <Link onClick={() => setState(!blocked)}>Toogle {blocked ? 'true' : 'false'}</Link>
    </View>
  );
}