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

ui/results: map options for results were not piping through properly #66

Merged
merged 3 commits into from
Jul 17, 2019

Conversation

b1lly
Copy link
Contributor

@b1lly b1lly commented Jul 16, 2019

immediate fix, may need to investigate further.

@b1lly b1lly requested a review from Delerme July 16, 2019 20:40
Copy link
Contributor

@Delerme Delerme left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

causes an error in vertical results because 'data' is frozen, so the object can't be extended

@b1lly
Copy link
Contributor Author

b1lly commented Jul 17, 2019

Manually Tested:

Components:
-Navigation
-Map
-Search (Vertical and Universal)
-Results
-UniversalResults

@b1lly b1lly requested a review from Delerme July 17, 2019 17:48
@b1lly b1lly merged commit b8e0899 into v0.7.2 Jul 17, 2019
Delerme pushed a commit that referenced this pull request Jul 19, 2019
Instead of the parent providing the data to the sub components during render, the sub components should be initialized with data from the parent, and then use local state for rendering.
@b1lly b1lly deleted the map branch July 19, 2019 19:07
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

Successfully merging this pull request may close these issues.

None yet

2 participants