-
Notifications
You must be signed in to change notification settings - Fork 53
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
Proposal: Add default pair for operations #484
Conversation
we should handle conflict. | ||
Since the operations with the same name handle different targets (`Servicer` and `Storager`), | ||
I think we should handle the separately. | ||
```go |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add empty line here.
|
||
Since one service may just implement a part of operations in [storage], | ||
there are two ways to define default pairs struct: | ||
- Unify struct in [storage], so that we can maintain it only once. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add empty line here.
and make sure that `pairs from args` can overwrite default pair, and this should be **generated**. | ||
For example, we parse the pairs sequentially from the slice of pairs, | ||
so we should create a new slice of pairs and append `pairs from args` to the slice. | ||
```go |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add empty line here.
No description provided.