radius-project / radius-project/radius
UDT - Miscellaneous: areas to revisit
Open
Nobody has claimed this yet.
triaged
- Dominant language
- Go
- Stars
- 1.7k
- Forks
- 137
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 110
Description
-
Approach to saving properties under "binding". This will require PM input to agree on a term that will replace "binding".
Ref: https://github.com/radius-project/radius/pull/8267#discussion_r1978631063 -
Revisit need for this check for nil status.
Ref: https://github.com/radius-project/radius/pull/8267#discussion_r2004028783
Contributor guide
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 8267 and its linked discussions. Clarify the replacement term for “binding” with PM input and decide whether the nil-status check is still needed. Done means both decisions are agreed, the affected UDT behavior is updated, and relevant validation is complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100