StatefulComponents to be made @client by default

[ShubhamVG]

For beginners, StatefulComponents kinda creates confusion when a it doesn't work/behave the way it is intended. e.g., setState not working (because @client was missing).

The above is neither a bug nor a bad design IMO. However, StatefulComponents are used when state is being played around with, which only happens with a client, no?

To be noted that I've only used Jaspr for SSG so far, not SSR. Hence, I am not sure if StatefulComponents are/do get used to deal with the logic of the server itself. It looks very possible but I couldn't think of a pragmatic situation myself. May I request some example cases? Maybe one with @sync on top of the StatefulComponent is one where it might be helpful.

[schultek]

StatefulComponents on the server don't really do anything. Because on the server only a single build is performed, meaning any build() method is only called once. Calling setState() is prohibited for the same reason (there are no rebuilds on the server).

Though as you correctly said, you can use StatefulComponents on the server with @client to make it interactive on the client.
Or with @sync to load some initial state on the server and sync it to the client for further use.