[packages] `Color.value` is deprecated

[stuartmorgan-g]

   info • [...] • 'value' is deprecated and shouldn't be used. Use
          component accessors like .r or .g, or toARGB32 for an explicit conversion. Try replacing the use of the
          deprecated member with the replacement. • deprecated_member_use

It's mostly used in plugins where we are serializing colors for method channels. In those cases, it would probably be best to make a PlatformColor class and get each component, rather than relying on matching bit operations on both sides as we currently do.

[JCKodel]

What is the logic of deprecating .value and allowing Color(0xaarrggbb)?

.value is important to color serialization! Why it has to be deprecated????

And, most importantly, why deprecate it while .toARGB32() is not implemented?

[ValeriusGC]

We are using handy convert color.value.toRadixString(16).padLeft(8, '0')} and how we should do this now?

[FluffyBunniesTasteTheBest]

Would be interesting to know what lead to the decision to deprecate Colors.value.

Now we need to serialize each color component individually, causing more sloc. Beside that it's more expensive in terms of io. And then there's the negative impact on the API, as @JCKodel already pointed out. A dedicated PlatformColor class would work, as @stuartmorgan pointed out, but then we'll find ourselfs converting forth and back...

All in all, this looks to me as if it would better be un-deprecated...

[stuartmorgan-g]

This issue is tracking updating the packages in the flutter/packages repository based on a deprecation that happened in the framework. It is not the place to request changes to Color, or to litigate the deprecation itself. These are simply clients of the API.