[Feature Request] Remove RetryState.RETRY_STATE_IN_PROGRESS from public api
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- grpc
- Domain
- api
Research direction
The enum declaration is in temporal/api/enums/v1/workflow.proto around line 107. Start by reviewing RetryState.RETRY_STATE_IN_PROGRESS and the API compatibility expectations; done means this internally used state is no longer exposed through the public API.
Written by the indexing model from the issue text.
Description
RetryState.RETRY_STATE_IN_PROGRESS
is used internally only but is exposed via public api: https://github.com/temporalio/api/blob/master/temporal/api/enums/v1/workflow.proto#L107
This is causing some confusions to our users. If possible please remove it (keep it internal only).
Idk if this should be issue opened on the server or here. Please let me know if this repo is wrong place for it.
- Dominant language
- Go
- Stars
- 133
- Forks
- 101
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 11
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from temporalio/api
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 58/100
temporalio/api#750 ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
temporalio/api#427 · 1 comment ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 45/100
temporalio/api#421 ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
temporalio/api#400 ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
temporalio/api#328 · 6 reactions ·
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
crossplane/crossplane#7859 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
bazel-contrib/rules_go#4721 · 2 comments ·
-
needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
bug carvel-triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
carvel-dev/kapp-controller#1861 ·
-
area/logging kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100