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
We should make it easier for template authors to create per-architecture defaults/options by providing the current host RID as another symbol/bindable value.
Describe the solution you'd like.
We should provide two new symbols to allow template authors to condition code/assets/symbols/etc based on host OS and host architecture.
HostPlatform // e.g. win, macos, linux - the first part of the RID. May be dynamic because it is powered by the RID graph.
HostArchitecture // eg. x64, arm64, x85 - the second logical part of the RID. May be dynamic because it is powered by the RID graph.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Yeah, exactly - then if we needed an override or to change/let the user specify a different one there might be a Target* variant of those same properties.
Is your feature request related to a problem? Please describe.
Today we provide the following Host-provided symbols for binding:
We should make it easier for template authors to create per-architecture defaults/options by providing the current host RID as another symbol/bindable value.
Describe the solution you'd like.
We should provide two new symbols to allow template authors to condition code/assets/symbols/etc based on host OS and host architecture.
Additional context
No response
The text was updated successfully, but these errors were encountered: