microsoft / microsoft/WindowsAppSDK
Remove non-functional APIs that always return null, like Window.Current
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 4.7k
- Forks
- 471
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 28
Description
This is the follow-on task from #1660. There are several APIs in our API surface that always return null and confuse developers, like `Window.Current` and also `Window.Dispatcher` and more. The presence of these non-functional APIs makes it more difficult to code and more difficult to migrate from UWP, since any developer would expect these APIs to work since they're there, but they actually just return null.
These APIs only worked in UWP, which was why we had them, but we need to clean up the API surface.
**Expected behavior**
We'll mark these APIs as deprecated with #1660, this issue tracks removing these APIs in 2.0.
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 by reviewing the deprecation work in #1660 and the APIs named here, including Window.Current and Window.Dispatcher. Confirm the full set of non-functional APIs covered by this follow-on task; done means those APIs are removed from the Windows App SDK surface for 2.0.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- api, desktop
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100