Clean up "Should be removed" fields
Open
Nobody has claimed this yet.
bug
- Dominant language
- Go
- Stars
- 133
- Forks
- 101
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 11
Description
In https://github.com/temporalio/api/pull/121 I added a few "Should be removed" comments to some fields. Remove them and mark them as reserved. Was not done in that PR to avoid doing any non-comments changes.
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.
Research direction
Start with pull request 121 and locate the fields carrying the "Should be removed" comments. Remove those comments and mark the corresponding fields as reserved; the work is done when the affected API definitions reflect both changes and the repository validation passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc
- Domain
- api, backend-api-design
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100