`@azure-tools/typespec-azure-core/invalid-final-state` error could be slightly improved for missing header
- Dominant language
- TypeScript
- Stars
- 27
- Forks
- 90
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 164
Description
Right now it says
```
There was no header corresponding to the desired final-state-via value 'azure-async-operation'.
```
but you now have to go look at the doc to see what is the header name in question.
[Playground Link](https://azure.github.io/typespec-azure/playground?c=aW1wb3J0ICJAdHlwZXNwZWMvaHR0cCI7CtIZcmVzdNUZdmVyc2lvbmluZ8wfYXp1cmUtdG9vbHMvyCstxhVjb3Jl3yvIK3Jlc291cmNlLW1hbmFnZXIiOwoKdXNpbmcgVHlwZVNwZWMuSHR0cDvQFVJlc3TRFVbpAKnIG0HEZS5Db3JlzhJSx3dNxnY7CgovKiogQ29udG9zbyDIHiBQcm92aWRlciDmAJ5tZW50IEFQSS4gKi8KQGFybcggTmFtZXNwYWNlCkBzZXJ2acQJ5wE2ZWQo5wCXcykKbsgoIE1pY3Jvc29mdC7HdchLSHVi7wCOQVBJIMdNc8R5ZW51bSDIVCB7CiAgxC4yMDIxLTEwLTAxLXByZXZpZXfINcQ0ICBAdXNlRGVwZW5kZW5jeSj1AQfoAUFzLnYxXzBfUMZIXzEpxEBhcm1Db21tb27kAW9zxyrXSMspy1Q1xEhg8gCpYCwKfeYA80HoAPXrAQ4g6AIj5ADIbW9kZWwgRW1wbG95ZWUgaXMgVHJhY2tlZOgAgjzIHFByb3BlcnRpZXM%2B5QEkLi7pAKbkAa5QYXJhbWV0ZXLJMT476ACGyV9wyUTSfMpg6QGDQWdlIG9mIGXIP%2BUBeGFnZT86IGludDMyOwrHKUNpdHnSKmNpdHk%2FOiBzdHLlAsHHLFByb2ZpbNNZQGVuY29kZSgiYmFzZTY0dXJsIuQBYHDGMD86IGJ5dGVzyUhUaGUgc3RhdHVzxEt0aGUgbGFzdCDkAMVhdGlvbuUC1CAgQHZpc2liaWxpdHkoInJlYWTIVcQY5QNbU3RhdMRf5QGjzBTpAUDEa8wyxXjlAMJh6QHNxW9AbHJvxDt1cwp1buQCqtFU5QFc5gESLOwAyshHIGNyZcQncmVxdWVzdCBoYXMgYmVlbiBhY2NlcHRlZMRnICBBxw46ICLICyLWUGnEQOQAtOkAwchE7ACcOiAizA%2FaTHVwZGF0xE%2FFQ1XHDjogIsgLyjvpBHXpAMTmANxk5wGaU3VjY2VlZOUAxckM0z%2FFNuQBTWZhaWzJPkbFDTogIsYJ3Dh3YXMgY2FuY2XKPkPHDzogIsgL%2FwFAIGRlbGXpAYBExA3mAPnICyLpA%2FXpA29tb3bqAcrpA3FNb3ZlUscV6ANqxHNtb3bEaGZyb20gbG9j5gC8xW7EE%2FEDSMszdG%2FPMXRvyi%2F3AJVzcG9uc%2BsEg%2BYAlscW7ACX7gNkxT7FZMZ85gLuym4vLyAgQGhlYWRlcigi5QVMLUFzeW5jT%2BgDlyIpIOUHKc4WyUEg5ACwaW50ZXJm5AZWySFzIGV4dGVuZHP2BvAuyyl7fQrlBszII8oby1noAQ%2FmBO1nZXTkAelByjVSZWFk7AVKICAvL%2BcCwE9y5QLs5QIbyzJDxx1SZXBsYWPmAODRQuUDP9A6UGF0Y2hTzC8s8wWWyEPmAojPQ%2BUChWVXaXRob3V0T2vWfWxpc3RCecgzR3JvdXDPR0zFIlBhcmVudNc%2FU3Vic2NyaXDlAm3GPsY2zBnMPOgGTCBzYW1wbOsDWmFjxUR0aGF05gJX6QYPdG8gZGlmZmXkAIfvAtpA6gkBLnVzZUZpbmFs5QVZVmlhKCLmCYNh5AD%2BLekGCeUF8cVh7gDtQeUAgO4BKyzsA57IDeYDFecAyy%2FuAM5IRUFE6gZ05AC6Y2hlY2vqAOZleGlzdGVu5gfuxUDFIUXJF%2B8CRs0d7gfM&e=%40azure-tools%2Ftypespec-autorest&options=%7B%22linterRuleSet%22%3A%7B%22extends%22%3A%5B%22%40azure-tools%2Ftypespec-azure-rulesets%2Fresource-manager%22%5D%7D%7D)
Contributor guide
Research direction
Start by locating the `@azure-tools/typespec-azure-core/invalid-final-state` diagnostic and reproduce it with the linked Playground example. Update the missing-header message so it identifies the header name, then verify the diagnostic wording against that example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend-api-design
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100