Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PSP-7158 Allow moving the position of map markers (within the file) #4233

Merged
merged 15 commits into from
Aug 7, 2024

Conversation

asanchezr
Copy link
Collaborator

video.mp4

@asanchezr asanchezr added the enhancement New feature or request label Jul 31, 2024
@asanchezr asanchezr self-assigned this Jul 31, 2024
Copy link
Contributor

✅ No secrets were detected in the code.

2 similar comments
Copy link
Contributor

✅ No secrets were detected in the code.

Copy link
Contributor

✅ No secrets were detected in the code.

Comment on lines 269 to 270
repositioningFeatureDataset: LocationFeatureDataset | null,
index: number | null,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can these be null if they are necessary for the state?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good catch - will change

actions: [
assign({
repositioningFeatureDataset: () => null,
repositioningPropertyIndex: () => null,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does selectingComponentId need to be set to null as well?

@@ -206,7 +219,7 @@ const MapLeafletView: React.FC<React.PropsWithChildren<MapLeafletViewProps>> = (
))}
</LayerGroup>
)}
{mapMachine.showPopup && (
{mapMachine.showPopup && !mapMachine.isRepositioning && (
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is kinda odd. The mapMachine should be the sole authority in deciding if the popup should be shown. Otherwise, we risk having the logic distributed. Would it be possible to have the state so both showPopup and isRepositioning can never happen together?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated

Copy link
Contributor

github-actions bot commented Aug 2, 2024

✅ No secrets were detected in the code.

Copy link
Contributor

github-actions bot commented Aug 3, 2024

✅ No secrets were detected in the code.

Copy link
Contributor

github-actions bot commented Aug 6, 2024

✅ No secrets were detected in the code.

@asanchezr asanchezr merged commit b678d7f into bcgov:dev Aug 7, 2024
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants