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

Move to Data-down, Actions-up architecture #97

Open
steveszc opened this issue Apr 13, 2017 · 0 comments
Open

Move to Data-down, Actions-up architecture #97

steveszc opened this issue Apr 13, 2017 · 0 comments

Comments

@steveszc
Copy link
Collaborator

As discussed in #84 there are opportunities to transition to a data-down actions-up architecture from the current architecture that prefers methods as API between components.

Considerations:

  • maintain backwards compatibility
  • account for syncing of state between g-map components and the underlying google.map object
  • account for google.map state management that is shared between g-map components
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