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
There is a lot of duct-tape in Spectre.Console to handle the differences between different environments.
It would be great if there was some kind of profile support that contained all the detected settings and capabilities from a specific environment (Windows, Linux, GH actions, TeamCity) and also made it overridable by the consumer of Spectre.Console.
For example:
GitHub actions support ANSI, but they're not a TTY so cursor movement should not be used. They also don't support links.
Since GitHub actions isn't a TTY, we can't query the buffer width so we always default to 80 columns which aren't really what we want to do.
The same goes with other environments such as running Windows apps under WSL. See #216 for more information
It would be great if components could query the supported features of the current environment via a profile on RenderContext or similar.
The text was updated successfully, but these errors were encountered:
There is a lot of duct-tape in Spectre.Console to handle the differences between different environments.
It would be great if there was some kind of profile support that contained all the detected settings and capabilities from a specific environment (Windows, Linux, GH actions, TeamCity) and also made it overridable by the consumer of Spectre.Console.
For example:
GitHub actions support ANSI, but they're not a TTY so cursor movement should not be used. They also don't support links.
Since GitHub actions isn't a TTY, we can't query the buffer width so we always default to 80 columns which aren't really what we want to do.
The same goes with other environments such as running Windows apps under WSL. See #216 for more information
It would be great if components could query the supported features of the current environment via a profile on RenderContext or similar.
The text was updated successfully, but these errors were encountered: