barrett/pending.nvim
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 2

refactor(config): remove legacy gcal top-level config key (#51)

Browse source 
* refactor(config): remove legacy gcal top-level config key

Problem: the gcal migration shim silently accepted vim.g.pending = { gcal
= {...} } and copied it to sync.gcal, adding complexity and a deprecated
API surface.

Solution: remove the migration block in config.get(), drop the cfg.gcal
fallback in gcal_config(), delete the two migration tests, and clean up
the vimdoc references. Callers must now use sync.gcal directly.

* ci: fix

* fix(spec): remove duplicate buffer require in complete_spec
This commit is contained in:
Barrett Ruth 2026-02-26 22:53:51 -05:00
parent ef58f69f74
commit 0cdb4e6dd6
5 changed files with 9 additions and 49 deletions
Download patch file Download diff file Expand all files Collapse all files

9
doc/pending.txt
View file

@ -631,12 +631,6 @@ Fields: ~
name and the value is the backend-specific config
table. Currently only `gcal` is built-in.
{gcal} (table, default: nil)
Legacy shorthand for `sync.gcal`. If `gcal` is set
but `sync.gcal` is not, the value is migrated
automatically. New configs should use `sync.gcal`
instead. See |pending.GcalConfig|.
{icons} (table) *pending.Icons*
Icon characters displayed in the buffer. Fields:
{pending} Uncompleted task icon. Default: '○'
@ -881,9 +875,6 @@ Configuration: >lua
}
<
The legacy `gcal` top-level key is still accepted and migrated automatically.
New configurations should use `sync.gcal`.
*pending.GcalConfig*
Fields: ~
{calendar} (string, default: 'Pendings')