[If this is a relatively large or complex change, start a discussion by explaining why you chose the solution you did and what alternatives you considered, etc...]
How To Test
[Provide whatever information a reviewer might need to know in order to verify that the changes made in this PR are working as expected. If there are special build steps that need to be taken in order to get these changes to run (building while on a separate branch, running npm ci, etc) include them here.]
For bugfixes: What steps need to be taken in the UI to verify the bug is fixed?
For enhancements and features: What is the expected functionality being added/modified? How can a reviewer verify this?
Open with these URL parameters
...
Verify expected result
PR Submission Checklist
This is simply a reminder of what we are going to look for before merging your code.
Main v4.41.0 to develop
Description
Fixes # .
[Description of the bug or feature]
[If this is a relatively large or complex change, start a discussion by explaining why you chose the solution you did and what alternatives you considered, etc...]
How To Test
[Provide whatever information a reviewer might need to know in order to verify that the changes made in this PR are working as expected. If there are special build steps that need to be taken in order to get these changes to run (building while on a separate branch, running
npm ci, etc) include them here.]PR Submission Checklist
This is simply a reminder of what we are going to look for before merging your code.
Merging
Please use the
squash and mergecommit method unless each commit in your branch is vital to the commit history of main.@nasa-gibs/worldview