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

[Docs] High level overview on URL recommendations and how state containers plays a role #76288

Closed
stacey-gammon opened this issue Aug 31, 2020 · 2 comments · Fixed by #76888
Closed
Assignees
Labels
needs_docs Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@stacey-gammon
Copy link
Contributor

In order to help plugin developers prefer one way to do things, we should add documentation around best practices regarding URL handling and where state containers and state syncing utilities fits into the picture.

Specifically I think we need to address when using these utilities makes sense (e.g. if an app follows the historical pattern of storing app state in _a and global state in _g), and when it doesn't.

Some questions I can think of:

  • If an app stores a minimal amount of state in the url, does it need to use these utilities at all, or should it use native react URL handling?
  • Should an app choose state containers over redux, if so why or in what circumstances?
@stacey-gammon stacey-gammon added Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Team:AppArch labels Aug 31, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app-arch (Team:AppArch)

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-platform (Team:Platform)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs_docs Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants