Some state could be in a parameter, or a cookie, or an actual session, or in Redis.
But having the way of state handling part of the View feels a little icky, too tightly scoped.
Helge Heß on Nostr: I'm thinking about how to do SwiftWebUI in a useful way. A big thing in web is state ...
I'm thinking about how to do SwiftWebUI in a useful way. A big thing in web is state handling, i.e. what would `@State` mean? In SwiftWebUI/WO this is just part of an in-server, sticky, session. Which is almost never what you want (and probably shouldn't be a convenience default).
Some state could be in a parameter, or a cookie, or an actual session, or in Redis.
But having the way of state handling part of the View feels a little icky, too tightly scoped.
Some state could be in a parameter, or a cookie, or an actual session, or in Redis.
But having the way of state handling part of the View feels a little icky, too tightly scoped.