task/WG-401-Add-Asset-to-Feature-Hook

[sophia-massie]

Overview:

Adds hook with hardcoded values to add an asset to a feature

PR Status:

• Ready.
• Work in Progress.
• Hold.

Related Jira tickets:

• WG-401

Summary of Changes:

Testing Steps:

1. On local staging env, open a map you've created with an existing geojson with no associated assets. It should look something like this
   
2. If you don't have a map of your own that you can edit with a geojson, go to deployed Hazmapper staging, open your map, and add a geojson from PROJ-4185 GEOAPI - Test project data (DO NO EDIT) to your separate map. Note - don't edit PROJ-4185 itself, import the feature to your own map.

3. Back on local staging, navigate to your map and select that geojson from Assets.
4. Click add Add Asset from DesignSafe
5. The button show show loading state then be disabled
6. Refresh the page as is (keeping the &selectedFeature param) and make sure that asset now has a picture of a beagle and the name in the Asset Panel now reflects the name of the image. (This will be a hardcoded asset to add to the feature).
   /TODO Replace with passed in values from FileBrowserModal. These are hardcoded to test./

UI Photos:

Final Result

Notes:

• Implement FileBrowserModal to get system_id and path to import.
• Create tests
• On successful submit, refresh AssetDetail panel to show new associated asset.

[nathanfranklin]

The use of isSuccess to disable the button is a good idea 💯. but needs to be specific to a particular feature (i.e. projecteId + featureId) and then the mutation's isSuccess is also tricky as it is not cached. 🤔 Let's just make a mental note and revisit this in February.

[sophia-massie]

Definitely. I will note to build out the hook state and button handling to be more robust when I'm using the modal to handle the submit.

[nathanfranklin]

LGTM 👍 🦖