-
Notifications
You must be signed in to change notification settings - Fork 95
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
Add monoids for options #75
Comments
Add a way for users to compose multiple options into one. Fixes #75.
What is the purpose of this? I don't immediately get it |
Imagine your organization (like Buf!) has a standard collection of options that you'd like every handler, client, or both to use. Without this, you end up with a fairly unpleasant set of APIs:
With these functions, life's a bit nicer.
Ultimately, it's convenient for users to be able to make a single option have multiple effects. More or less, this is the same reason your proposal to build a multi-plugin for protoc/buf is nicer than forcing every tool to take a list of plugins to generate into the same directory. |
Examples from other packages I've worked on: Both of those options ended up pretty widely used, and the |
I'm not sure this will be as used in the connect world and it just adds to the number of types, but you feel strongly about it and it's fine with me. I might say that |
Add a way for users to compose multiple options into one. Fixes #75.
Add a way for users to compose multiple options into one. Fixes #75.
I think we should let users remix options. It's hard to do this from outside connect because the options interfaces have unexported functions.
The text was updated successfully, but these errors were encountered: