Alexandru Mariuti is on @buymeacoffee! 🎉 You can support by buying a ☕️ here —

@gochev @RydMike @mickrich384 @michael_lazebny Would install it immediately 😅

@mickrich384 @jezell @SuprDeclarative @FlutterDev Not true for lucide_icons_flutter It's a font

@jezell @mamagnus00 Langchain 🤮

@RydMike @mickrich384 @michael_lazebny I remember I tried to add Color.fromHex and Color.toHex without success. Because there is no way to extend a class with a static methods. So withOpacity can be added back with an extension?

@RydMike @caseycrogers Yes I'm making it stunning among others in a branch I'm working, you'll see when I release the v2

@mickrich384 @michael_lazebny Or unless the solution can be already solved with some basic extensions. But for the Color class extensions do not work unfortunately if I remember correctly 🥲

@caseycrogers @FlutterDev Yes seems the simple version of the solidart Resource. Great job 👏

@caseycrogers If a user needs a different ways to change a signal value, (s)he can write extensions. Will provide a very simple but extensible API

@caseycrogers You can always access synchronously the value of a resource. Not like Streams where you need RxDart with a BehaviorSubject or caching the value.

@ChotiMelky i'm on it

RT @SuprDeclarative:

@SuprDeclarative Documentation

@SEGVeenstra @codeonsunday @nankiro In reality it's impossible not to use (import) material, the Color class for example is exported by material. BTW, no big impact. If you use ShadApp, WidgetsApp is used internally. If you use ShadApp.material, MaterialApp is used instead.

@mahersafadii @hamza_imran75 @FlutterDev

@SEGVeenstra @codeonsunday @nankiro yeah, exactly what he said. No need to reinvent the wheel for each component