Add a new name resolution method: structuredformat#4085
Add a new name resolution method: structuredformat#4085
Conversation
Signed-off-by: seal90 <578935869@qq.com>
Signed-off-by: seal90 <578935869@qq.com>
…contrib into config-string
mikeee
left a comment
mikeee
left a comment
There was a problem hiding this comment.
Looking good to me, could you please open up a docs PR?
Cheers!
|
Will do — I’ll open a docs PR . |
|
I've opened the docs PR — thanks for the review! |
sicoyle
left a comment
sicoyle
left a comment
There was a problem hiding this comment.
few comments so far. Can you also look at all the struct fields added and make them unexported by default where applicable please? Thank you for your contribution!! 🙌
Signed-off-by: seal90 <578935869@qq.com>
…contrib into config-string
|
Hello! I've fixed and optimized both the code and the documentation. |
|
This pull request has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in 7 days if no further activity occurs. Please feel free to give a status update now, ping for review, or re-open when it's ready. Thank you for your contributions! |
|
This pull request has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in 7 days if no further activity occurs. Please feel free to give a status update now, ping for review, or re-open when it's ready. Thank you for your contributions! |
|
This pull request has been automatically closed because it has not had activity in the last 37 days. Please feel free to give a status update now, ping for review, or re-open when it's ready. Thank you for your contributions! |
|
This needs to be reopened |
6 participants
Description
Add a new name resolution method: structuredformat.
Service invocation can be configured with just a simple text-based configuration.
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #[4084]
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:
Note: We expect contributors to open a corresponding documentation PR in the dapr/docs repository. As the implementer, you are the best person to document your work! Implementation PRs will not be merged until the documentation PR is opened and ready for review.