Alternative naming?

[wandymapn]

Hi, just curious. I’ve been using this solution in one of my projects, and it has really made working with state management much easier. Thanks for your hard work!

There’s just one thing that’s been bothering me. It’s not really a bug or a feature request, but more of a question:
Do you plan to simplify the @ annotation names?

For example:

@SolidState → @State

@solidEffect → @effect or @watch

Basically, removing the prefix.

I could wrap SolidProvider, but I’m not sure if wrapping @SolidState is possible as well (maybe it is?).

[nank1ro]

Hi 👋🏼

Be careful, the current version is error prone and not really production ready. I need to reimplement it from scratch to make it less error-prone and faster.

To answer your question, this was my first idea, but State is reserved in Flutter by the state of a StatefulWidget so it cannot be used.
Same for Effect, the package flutter_solidart (the state management used under the hood) uses Effect already.
That's why I prefixed every annotation with Solid.

I could wrap SolidProvider, but I’m not sure if wrapping @SolidState is possible as well (maybe it is?).

Not sure what do you mean, can't SolidState be inside the instance of the class you provide with SolidProvider?