Old code handled MAAP and VEDA STAC_BROWSER_URL differently, this assumed that the ENV variables were quite different. By standardizing how the ENV is supplied agnostic code can be used, and a fallback in the event of missing variable can also be handled.
Fixes or Addresses Issue #: [ticket number & link]
116
Checklist before requesting a review:
[x] My code follows the guidelines of this project
[x] I performed a self-review of my code changes
[x] I have added my changes to the change log (HISTORY.rst)
[x] I have completed spell-checking, removed unnecessary print statements & commented-out code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] New and existing unit tests pass locally with my changes
116
Always just sub BROWSER url for STAC url. Can better describe in docs what values are expected. See also https://github.com/MAAP-Project/stac_ipyleaflet/issues/116
Summary:
Old code handled MAAP and VEDA STAC_BROWSER_URL differently, this assumed that the ENV variables were quite different. By standardizing how the ENV is supplied agnostic code can be used, and a fallback in the event of missing variable can also be handled.
Fixes or Addresses Issue #: [ticket number & link]
116
Checklist before requesting a review:
HISTORY.rst)