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
Currently, the PSSA compatibility rules can only specify targets by name or path.
Compatibility target names are long, unintelligible and cumbersome.
Instead, users need to be able to do things like specify a list of PowerShell versions to target or a list of operating systems.
There needs to be a systematic, composable, human-readable way to specify these settings all the way from "everything" to "PowerShell 6.1 on Linux AND PowerShell 5.1 on Windows only".
While this resembles .NET RIDs, those form a simple lattice where the whole RID refers only to a granularity of operating system. A PowerShell platform can differ in operating system, PowerShell version, .NET version, .NET edition, machine architecture and process architecture (in decreasing order of importance).
The text was updated successfully, but these errors were encountered:
Currently, the PSSA compatibility rules can only specify targets by name or path.
Compatibility target names are long, unintelligible and cumbersome.
Instead, users need to be able to do things like specify a list of PowerShell versions to target or a list of operating systems.
There needs to be a systematic, composable, human-readable way to specify these settings all the way from "everything" to "PowerShell 6.1 on Linux AND PowerShell 5.1 on Windows only".
While this resembles .NET RIDs, those form a simple lattice where the whole RID refers only to a granularity of operating system. A PowerShell platform can differ in operating system, PowerShell version, .NET version, .NET edition, machine architecture and process architecture (in decreasing order of importance).
The text was updated successfully, but these errors were encountered: