You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 15, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Jun 15, 2026. It is now read-only.
I know I've brought this up before, but it seems odd that CoreTS needs to know about supported platforms.
Doesn't this indicate a poor separation between what's "core" what consumes the "core" library?
There appears to be a cyclical link between something that uses CoreTS and it needing to have information about what the things that use it want to do.
CoreTS is platform and language agnostic, but it's where Platforms and Languages are defined and validated (due to how things grew in the past).
We should split and move the Platforms and ProgrammingLanguages classes and move them to WebTS + WinTS.
Activity
mrlacey commentedon Nov 12, 2020
I know I've brought this up before, but it seems odd that CoreTS needs to know about supported platforms.
Doesn't this indicate a poor separation between what's "core" what consumes the "core" library?
There appears to be a cyclical link between something that uses CoreTS and it needing to have information about what the things that use it want to do.
sibille commentedon Nov 12, 2020
CoreTS is platform and language agnostic, but it's where Platforms and Languages are defined and validated (due to how things grew in the past).
We should split and move the Platforms and ProgrammingLanguages classes and move them to WebTS + WinTS.
sibille commentedon Dec 3, 2020
Created a separate issue for splitting and moving the Platform and ProgrammingLanguages classes in #282
prupipho commentedon Apr 28, 2021
Tested on nightly build:
Templates version: 0.3.21113.4
Wizard version: 0.3.2111304