milesj/boost

[2.0] Rework configBlueprint and settingsBlueprint

milesj opened this issue · 1 comments

Both of these Tool options require the consumer to explicitly install optimal. Let's try and remove this dependency, perhaps following blueprint(), and passing the predicates through a function.

new Tool({
  configBlueprint({ string }) {
    return { foo: string() };
  },
});

Core is being deprecated in v2, so this isn't necessary.