You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
zino.state is a module that holds the global/singleton root state object for the server, correct. The global state object in that module is also named state. As @stveit pointed out, this does turn into a "state soup" (e.g. state = state.state) and can get hard to read.
I've no problem with renames, but we need to agree on a naming system then. I could live with the module zino.server_state, but is the object zino.server_state.state any better?
zino.state
is a module that holds the global/singleton root state object for the server, correct. The global state object in that module is also namedstate
. As @stveit pointed out, this does turn into a "state soup" (e.g.state = state.state
) and can get hard to read.I've no problem with renames, but we need to agree on a naming system then. I could live with the module
zino.server_state
, but is the objectzino.server_state.state
any better?Originally posted by @lunkwill42 in #95 (comment)
The text was updated successfully, but these errors were encountered: