microsoft / microsoft/typespec
Invalidating sourceProperty on property mutation
Open
design:needed
- Dominant language
- Java
- Stars
- 5.9k
- Forks
- 394
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 104
Description
It was harder than I thought to make a repro using the playground, but theoretically, if a sourced property is modified (say by a projection), we should probably remove the sourceProperty. Things like getEffectiveType would consider the changed property and its source to be equivalent. Pretty much everywhere we check sourceProperty in this case is questionable.
Contributor guide
Assessment
This issue has not been assessed yet.