Replies: 1 comment 1 reply
-
More like (mostly) a side effect of early days of the project getting rolling. Some early features were spec'd using Windows' traditional tools and processes and not per the current WinAppSDK process (markdown docs under Going forward this generally shouldn't occur. WinAppSDK's policy is to default to open/public specs and code, unless there's good reason to be closed/private (e.g. IP or like secrets that cannot be disclosed). Was there something in particular you were looking for or you happened to notice the gap and inquired? |
Beta Was this translation helpful? Give feedback.
-
As title.
Beta Was this translation helpful? Give feedback.
All reactions