Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[2.0] Rework configBlueprint and settingsBlueprint #35

Closed
milesj opened this issue Jan 31, 2019 · 1 comment
Closed

[2.0] Rework configBlueprint and settingsBlueprint #35

milesj opened this issue Jan 31, 2019 · 1 comment

Comments

@milesj
Copy link
Owner

milesj commented Jan 31, 2019

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() };
  },
});
@milesj
Copy link
Owner Author

milesj commented Jun 22, 2020

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

@milesj milesj closed this as completed Jun 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant