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

app, ui, server #59

Open
jonthegeek opened this issue Feb 7, 2024 · 0 comments
Open

app, ui, server #59

jonthegeek opened this issue Feb 7, 2024 · 0 comments

Comments

@jonthegeek
Copy link
Contributor

De-cute the names a bit. And, now that I grok that we can change the server (by wrapping all servers in a wider server function that decides which one to call), I think the most common use case will be wrapping an entire ui + server, and only occasionally will people want to separately wrap UI and server. Note that under the hood they're still independent somewhat, because ui is decided using request, while server is via session$request.

  • Keep set_scene() and change_scene(), although possibly with a deprecation warning.
  • Those will just be aliases for set_ui() and change_ui().
  • Add set_app() and change_app()
  • Add set_server() and change_server()

Split this into multiple tickets if necessary, but I suspect I can do most/all of it at once cleanly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant