Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discuss how to meaningfully name/rename zino.state and zino.state.state et.al #127

Open
lunkwill42 opened this issue Nov 28, 2023 · 0 comments
Assignees

Comments

@lunkwill42
Copy link
Member

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?

Originally posted by @lunkwill42 in #95 (comment)

@lunkwill42 lunkwill42 self-assigned this May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant