Skip to content

Conversation

@williscool
Copy link
Owner

@williscool williscool commented Apr 10, 2025

TODO

  • I would exclude reccuring events from this its hard to tell if you are dismissing the right one (we look ahead a year and another part of the codebase always picks the latest event so that could mean we dissmiss based on a future version of a reccuring event) will handle in Fast Follows: we need to exclude recurring events from Reschedule Confirmations dismissals #81
  • we should documetn (called it ! lol alter publication powersync add table public.reschedule_confirmations)

  • feat: dismiss from reschedule confirmations!
  • feat: ids array over the bridge!
  • feat: json over the bridge!
  • feat: stub for in the app
  • feat: events all the way to the app side!
  • feat: maybe dismiss from react native!
  • feat: updated dissmiss message
  • feat: safe dismiss in bulk
  • test: tests!
  • chore: interface
  • test: event dissmiss tests run
  • test: ignore orig tests for now

@williscool williscool changed the title feat/dismiss from reschedule confirmations feat!: dismiss from reschedule confirmations Apr 10, 2025
@github-actions
Copy link

Build artifacts for this PR are available:

You can download these artifacts from the "Artifacts" section of the workflow run.

@github-actions
Copy link

Build artifacts for this PR are available:

You can download these artifacts from the "Artifacts" section of the workflow run.

@github-actions
Copy link

github-actions bot commented Apr 11, 2025

Code Coverage Report

Overall Project 13.77% -1.19%
Files changed 28.66%

Module Coverage
app 26.25% -0.72%
x8664Debug 1.43% -1.66%
Files
Module File Coverage
app EventDismissResult.kt 90.79% -9.21% 🍏
DismissedEventAlertRecord.kt 57.69% -12.5% 🍏
ApplicationController.kt 37.22% -8.19%
RescheduleConfirmationsBroadcastReceiver.kt 0%
DismissedEventListAdapter.kt 0% -3.04%
x8664Debug DismissedEventListAdapter.kt 0% -3.04%
RescheduleConfirmationsBroadcastReceiver.kt 0%
ApplicationController.kt 0% -19.55%
EventDismissResult.kt 0%
DismissedEventAlertRecord.kt 0% -37.5%

@github-actions
Copy link

📊 Code Coverage Summary

Type Coverage
Line 13.53
Branch

View detailed coverage report

@github-actions
Copy link

Build artifacts for this PR are available:

You can download these artifacts from the "Artifacts" section of the workflow run.

@github-actions
Copy link

📊 Code Coverage Summary

Type Coverage
Line 13.52
Branch

View detailed coverage report

@github-actions
Copy link

📊 Code Coverage Summary

Type Coverage
Line 13.49
Branch

View detailed coverage report

@github-actions
Copy link

Build artifacts for this PR are available:

You can download these artifacts from the "Artifacts" section of the workflow run.

@github-actions
Copy link

📊 Code Coverage Summary

Type Coverage
Line 13.98
Branch

View detailed coverage report

@github-actions
Copy link

Build artifacts for PR #73 (commit 932424f) are available:

You can download these artifacts from the "Artifacts" section of the workflow run.

@github-actions
Copy link

📊 Code Coverage Summary

Type Coverage
Line 13.87
Branch

View detailed coverage report

@github-actions
Copy link

Build artifacts for PR #73 (commit 238f42e) are available:

You can download these artifacts from the "Artifacts" section of the workflow run.

@github-actions
Copy link

📊 Code Coverage Summary

Type Coverage
Line 0.72
Branch

View detailed coverage report

@github-actions
Copy link

Build artifacts for PR #73 (commit 17297f2) are available:

You can download these artifacts from the "Artifacts" section of the workflow run.

@github-actions
Copy link

📊 Code Coverage Summary

Coverage Type Coverage
Overall 13.63
Changed Files 13.93

View detailed coverage report

@github-actions
Copy link

Build artifacts for PR #73 (commit 2a11e61) are available:

You can download these artifacts from the "Artifacts" section of the workflow run.

@github-actions
Copy link

Build artifacts for PR #73 (commit 23d07b0) are available:

You can download these artifacts from the "Artifacts" section of the workflow run.

@github-actions
Copy link

📊 Code Coverage Summary

Coverage Type Coverage
Overall 13.64
Changed Files 13.93

View detailed coverage report

@github-actions
Copy link

📊 Code Coverage Summary

Coverage Type Coverage
Overall 13.73
Changed Files 14.18

View detailed coverage report

@github-actions
Copy link

Build artifacts for PR #73 (commit 377bbe5) are available:

You can download these artifacts from the "Artifacts" section of the workflow run.

@github-actions
Copy link

📊 Code Coverage Summary

Coverage Type Coverage
Overall 13.71
Changed Files 14.18

View detailed coverage report

@github-actions
Copy link

Build artifacts for PR #73 (commit 31a1798) are available:

You can download these artifacts from the "Artifacts" section of the workflow run.

@github-actions
Copy link

📊 Code Coverage Summary

Coverage Type Coverage
Overall 13.77
Changed Files 15.47

View detailed coverage report

@williscool williscool enabled auto-merge (squash) April 25, 2025 07:25
@williscool williscool mentioned this pull request Apr 25, 2025
20 tasks
@williscool williscool merged commit da17b07 into master Apr 25, 2025
10 checks passed
@williscool
Copy link
Owner Author

just saving some notes from working on this

TODO

  • I would exclude reccuring events from this its hard to tell if you are dismissing the right one (we look ahead a year and another part of the codebase always picks the latest event so that could mean we dissmiss based on a future version of a reccuring event)
  • we should documetn (called it ! lol alter publication powersync add table public.reschedule_confirmations)

done

issmiss events it finds cannot be undone

then it filters table for isInFuture and dissmiss!

DONT FORGET TO REMOVE THE DEV PAGE FROM THE BUILD THAT GOES ON YOUR PHONE!!!!

follow up clean uip

add a button that syncs schduler confirmations to local powesync db (it should be one way from powesync through the supabase resschduler confirmations table)

my-module consumes that put it behide a safe place that says will d

override fun dismissEvent(

context: Context,

dismissType: EventDismissType,

eventId: Long,

instanceStartTime: Long,

notificationId: Int,

notifyActivity: Boolean

) {

witht he eventId and instanceStartTime

should be ready for errors where they dont exist

ponly place I worry about snag is powersync setup. does teh pucliation name matter?

(called it ! lol alter publication powersync add table public.reschedule_confirmations)

notes dont forget to setup supabase table to be realtime and broadcast cahnges in their tabel (i dd it late night 4-9)

dont forget you can hardcode a record in reschuler confrimations to use also we can just locally hard code theid and call it from the js side of the bridge

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants