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

Fix/data products #536

Merged
merged 2 commits into from
Jun 8, 2023
Merged

Fix/data products #536

merged 2 commits into from
Jun 8, 2023

Conversation

Tammo-Feldmann
Copy link
Contributor

What I'm fixing

I created a bug while removing spatial bounds at the campaign level. The explore map didn't get correctly parsed bbox inputs anymore. I added that back in.

I also forgot to replace an tag with a link in the products table and made that replacement here.

How you can test it

You can now see the explore map render bounding boxes for all campaigns again rather than throwing an error 😉 .

@@ -49,7 +49,7 @@ const ExploreMap = ({ allData, filteredData, setGeoFilter, aoi, setAoi }) => {
}

// Compute and set the initial bounding box
const [bbox] = useState(() => turfBbox(geojson))
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Since there was nowhere that we were using a setter here, I removed the useState hook.

@edkeeble edkeeble merged commit 395d615 into develop Jun 8, 2023
@edkeeble edkeeble deleted the fix/data-products branch June 8, 2023 15:12
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.

2 participants