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

Display current mapper events to the user somewhere on mapper frontend #1980

Closed
spwoodcock opened this issue Dec 11, 2024 · 6 comments
Closed
Assignees
Labels
effort:low Likely a few hours enhancement New feature or request frontend Related to frontend code priority:low Backlog of tasks that will be addressed in time testing:ready Ready for testing

Comments

@spwoodcock
Copy link
Member

  • We only display the event stream in desktop mode.

Image

  • This should be available somewhere in mobile too, as long as we can make it not very intrusive.
@spwoodcock spwoodcock added effort:low Likely a few hours enhancement New feature or request frontend Related to frontend code priority:low Backlog of tasks that will be addressed in time labels Dec 11, 2024
@spwoodcock
Copy link
Member Author

This should probably be a small toast alert?

The top right doesn't seem like a bad spot out of the way.

I guess the main concern is that on very active projects, lots of notifications would impede on the mapper use experience (get in the way of the ui). Let's test it out and see

@manjitapandey
Copy link
Contributor

manjitapandey commented Dec 31, 2024

  • In mapper event, the taskID provided is different than task ID we show to users on tasks.
  • And also is the last mapper event only based on tasks status update or does it also includes change the status of features too?? If the event only shows tasks level updates then we should find a way to inform users that it doesn't include feature level update.
  • The time on current mapper event is not updated. I updated the task status 5 minutes ago but it still shows 0 minutes ago.

cc: @NSUWAL123

@manjitapandey manjitapandey added testing:fail Failed testing and removed testing:ready Ready for testing labels Dec 31, 2024
@NSUWAL123
Copy link
Contributor

  • In mapper event, the taskID provided is different than task ID we show to users on tasks.
  • And also is the last mapper event only based on tasks status update or does it also includes change the status of features too?? If the event only shows tasks level updates then we should find a way to inform users that it doesn't include feature level update.
  • The time on current mapper event is not updated. I updated the task status 5 minutes ago but it still shows 0 minutes ago.

cc: @NSUWAL123

@NSUWAL123 NSUWAL123 added testing:ready Ready for testing and removed testing:fail Failed testing labels Dec 31, 2024
@manjitapandey
Copy link
Contributor

How do we handle feature level events update??

And also is the last mapper event only based on tasks status update or does it also includes change the status of features too?? If the event only shows tasks level updates then we should find a way to inform users that it doesn't include feature level update.

If not possible in mapper's UI, I can include that on documentation somewhere to inform users that the latest event is only for feature level update once @NSUWAL123 provides me headsup.

@NSUWAL123
Copy link
Contributor

For now, I think showing feature-level events is not possible. As the feature is not live updated as the task, we need to hit the /entities/statuses API to sync the status for live update.
Am I right @spwoodcock?

@spwoodcock
Copy link
Member Author

Live feature level events can be obtained from the odk_entities table if we create another electric ShapeStream in the mapper frontend.

But the events will only be synced ODK --> FMTM (when mapped in ODK Collect) when the API endpoint you mention is called (for now). We will fix the real time updating usijg webhooks in the near future

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort:low Likely a few hours enhancement New feature or request frontend Related to frontend code priority:low Backlog of tasks that will be addressed in time testing:ready Ready for testing
Projects
Development

No branches or pull requests

3 participants