[Suggestion] Change 'Color' to 'SpectreColor'

[jeffward01]

Hello!

I suggest that 'Color' from Spectre.Console.Color is change to Spectre.Console.SpectreColor.

The reason for this change is that Color is incredibly popular, and has conflicting names in just about every single Console UI library.

I find myself every time when working with Spectre.Console that I must perform a using statement declaration of:

using Spectre.Console;
using SpectreColor = Spectre.Console.Color;   

Suggestion

I suggest: Spectre.Console.Color is changed to Spectre.Console.SpectreColor.

I know its a breaking change, I can see this being a 'blocker', due to this.

It will be a simple 'breaking change'.

[patriksvensson]

@jeffward01 I have personally never encountered that problem, and I don't see us changing to SpectreColor, to be honest.
In C# 10, you can add a global using once in your project, which should solve your problem:

global using SpectreColor = Spectre.Console.Color;

[jeffward01]

I agree, that:

global using SpectreColor = Spectre.Console.Color;

is a good solution, however I find myself doing this on all my projects.

Reasons

Also I see that (Spectre.Console.ImageSharp) is a popular extension for Spectre.Console, a library which I use often.

This library (Spectre.Console.ImageSharp) is a 'packaged' version of ImageSharp. The library ImageSharp (among many other libraries which are commonly used in console apps) use the class Color. Here is how Color is used in ImageSharp .

It is common that Visual Studio references the namespace SixLabors.ImageSharp instead of Spectre.Console.Colors because of the overlapping namespace names.

Summary

While I agree that the global using is a good solution, I feel that because many libraries use the Color class, including libraries which are integrated into extension libraries of Spectre.Console, it would be nice to have a unique naming concept of Color to SpectreColor.

I agree that this is more of a 'Convenience' and 'Cosmetic' fix and discussion, but I think it would make sense.

Proposal

However there would be breaking changes of course due to the class name change of Color to SpectreColor. So perhaps wait until the next major version release.

I love Spectre.Console and I just wanted to share my opinion on this.

Thanks!