Tags: developmentseed/stac-map
Tags
feat: added kyfromabove api to the examples (#178) I added Kentucky's STAC API as an example to the `src/contants.ts` file. I think it adds variety and another state to complement the *Colorado NAIP*. It might make the list too long, so I won't be upset if you don't want to include. ```json { title: "Kentucky Imagery & Elevation", badge: "API", href: "https://spved5ihrl.execute-api.us-west-2.amazonaws.com/", }, ``` <img width="292" height="347" alt="image" src="https://github.com/user-attachments/assets/e23eca7a-3f29-4485-bcc9-b5c3a9741b3c" /> ## Checklist - [x] Code is formatted (`yarn format`) - [x] Code is linted (`yarn lint`) - [x] Code builds (`yarn build`) - [x] Tests pass (`yarn test`) - [ ] Commit messages and/or this PR's title are formatted per [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) Co-authored-by: ianhorn <=>
fix: Remove fileUpload dep in useStacValue useEffect (#177) So when reviewing the error boundary PR #176 which I did a couple of days ago.. apologies for not approving and bringing this up sooner but I realized the app looked like it was infinitely rendering.. Is this supposed to happen?? If not, I went down a path trying to figure out where this was happening. It looked like the `useStacValue` hook's useEffect had a dep `fileUpload` which is hook from chakra that was causing this. This PR just removes that dep to stop the app from infinitely rendering. But maybe this could be solved another way? Either way, I dont think this should cause a big issue having that missing dep as I think it will still be stable enough. What do you think @gadomski? -------------------- **Behavior before (infinite render):** https://github.com/user-attachments/assets/d895a717-b039-4cf6-a59c-c963f7a2ee44 **Behavior now:** https://github.com/user-attachments/assets/0dcda900-f47b-4485-9b35-663a71e13222
fix: add an error boundary for each section (#176) This is a guardrail to keep a bad section from crashing the whole app. It's a bit of a hack until I can figure out what's going on with #174 I intentionally broke that section to check how it worked, this is what it looks like: <img width="821" height="341" alt="image" src="https://github.com/user-attachments/assets/1ecaf662-de94-4eff-b5e5-7fbe7a549266" /> ## Checklist - [x] Code is formatted (`yarn format`) - [x] Code is linted (`yarn lint`) - [x] Code builds (`yarn build`) - [x] Tests pass (`yarn test`) - [x] Commit messages and/or this PR's title are formatted per [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/)
PreviousNext