Barrett Ruth
90f1378cb6
Problem: `with_token` was duplicated in `gcal.lua` and `gtasks.lua`, with the concurrency lock added only to the gtasks copy. Any new backend would silently inherit the same race, and gcal back-to-back push could still create duplicate remote calendar events. Solution: lift `with_token` into `oauth.lua` as `M.with_token(client, name, callback)` behind a module-level `_sync_in_flight` guard. All backends share one implementation; the lock covers gcal, gtasks, and any future backend automatically. |
||
|---|---|---|
| .. | ||
| sync | ||
| buffer.lua | ||
| complete.lua | ||
| config.lua | ||
| diff.lua | ||
| health.lua | ||
| init.lua | ||
| log.lua | ||
| parse.lua | ||
| recur.lua | ||
| store.lua | ||
| textobj.lua | ||
| views.lua | ||