You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Since there are now 'Properties' and 'Related Properties' in the Info pane, it can lead to confusing UX if we add the same property as a related property.
To Reproduce
Steps to reproduce the behavior:
Click on a property boundary
Check for other properties
Highlight the same property
It now shows a duplicate item, but as a 'Related Property'
If we try to select one of the items, both items expand (since they are keyed off the same polygon ID, which should be unique and we assume is unique throughout lots of the app). The way that properties are highlighted when they are clicked/expanded also differs between Properties and Related Properties.
Expected behaviour
More consistent UX
Do we need to differentiate between 'Properties' and 'Related Properties' in the info pane? I'm wondering if we could just show them all as properties in the same way, including those that the user selects using backsearch. This would simplify the code a lot too. @ms0ur1s@lin-d-hop what do you think, since you maybe have more context about how this feature is being used
The text was updated successfully, but these errors were encountered:
@ms0ur1s Ah cool, no worries. So I'm thinking we could actually simplify the code a lot by just adding any related properties to the same collection of properties we already had in LandOwnershipReducer.
This would allow us to remove some duplicated code relating to related properties and the highlighting of them, which would speed up development.
I'll add to the bug backlog, since I think it can wait until after the current Backsearch P1 and P2 issues
Describe the bug
Since there are now 'Properties' and 'Related Properties' in the Info pane, it can lead to confusing UX if we add the same property as a related property.
To Reproduce
Steps to reproduce the behavior:
Expected behaviour
More consistent UX
Do we need to differentiate between 'Properties' and 'Related Properties' in the info pane? I'm wondering if we could just show them all as properties in the same way, including those that the user selects using backsearch. This would simplify the code a lot too.
@ms0ur1s @lin-d-hop what do you think, since you maybe have more context about how this feature is being used
The text was updated successfully, but these errors were encountered: