DigitalCommons / land-explorer-front-end

React app for the Land Explorer front end
http://landexplorer.cc
GNU Affero General Public License v3.0
1 stars 0 forks source link

Ownership Search: Related properties not highlighting on map #311

Open King-Mob opened 3 months ago

King-Mob commented 3 months ago

Describe the bug When using the ownership search to see related properties, the properties aren't highlighting on the map. And clicking on one property selects all of them.

To Reproduce Steps to reproduce the behavior:

  1. Turn on ownership search
  2. Select green property
  3. Click 'check for other properties'
  4. Click arrow next to one of the properties
  5. Click clear all, then click one of the properties in the list

Expected behaviour

  1. The properties highlighted in green should display on the map
  2. The properties should only be highlighted in green if they have been clicked on

Screenshots/GIFs lx bug property selection

Context (please complete the following information):

Additional context I checked to see if this was happening on my local version of the front-end. I haven't pulled from dev since I left the project. Connecting my local version to the staging back-end, this bug doesn't appear.

lin-d-hop commented 3 months ago

Strange that this has started failing in between a deployment. That is likely a clue...

ms0ur1s commented 2 weeks ago

Also, the Ownership Search panel remains populated when the Land Information panel has been cleared. I can't remember whether that's expected functionality, though.

The Ownership Search panel also remains populated with the last search when you switch between maps.

https://www.awesomescreenshot.com/video/28988449?key=2c3e132d4873a7804fa706e8cfc49ae4

ms0ur1s commented 2 weeks ago

The Ownership Search panel also remains populated with the last search when you switch between maps.

@lin-d-hop this definitely seems like a bug. Should I stick this in new ticket?

lin-d-hop commented 2 weeks ago

Let's leave this for now. I've noticed it in the past but it's a bug with a very easy work around.