aboutsummaryrefslogtreecommitdiff
path: root/runtime/lua/vim/provider/python.lua
diff options
context:
space:
mode:
authorEvgeni Chasnovski <evgeni.chasnovski@gmail.com>2025-08-02 14:58:03 +0300
committerEvgeni Chasnovski <evgeni.chasnovski@gmail.com>2025-08-02 15:00:42 +0300
commited73ed82837455ad5dae6d6917a20c3679016343 (patch)
treebf5729051fad4b1b58bd0545a0cc4fea00c8fb23 /runtime/lua/vim/provider/python.lua
parent8200223ee7a8dd9882367582c4a6e1d280012fff (diff)
downloadrneovim-ed73ed82837455ad5dae6d6917a20c3679016343.tar.gz
rneovim-ed73ed82837455ad5dae6d6917a20c3679016343.tar.bz2
rneovim-ed73ed82837455ad5dae6d6917a20c3679016343.zip
fix(pack): ensure explicit default `version` in events (where possible)
Problem: Both `PackChangedPre` and `PackChanged` contain |event-data| with plugin's `spec`. It looks like a good idea to have all its triggers contain the same format across all kinds ("install", "update", "delete"). There are several choices: - Have it be as verbatim as supplied to `vim.pack.add()`, i.e. can be either string or table. A bit too ambiguous. - Have it be table with `src` and `name` inferred. This requires less work for "install", but more work for "update" and "delete" (since they use `vim.pack.get()` which already infers default `version`). - Have it be table with *all* defaults made explicit. This looks like the best approach, but requires extra care to only infer default `version` when needed (i.e. avoid inferring during regular load) because it is costly in terms of startup time. This might also introduce inconsistency when dealing with lockfile(s) as information there should be as close to what user supplied as possible. Address that when dealing with lockfile. Solution: Ensure explicit `version` in all events where possible.
Diffstat (limited to 'runtime/lua/vim/provider/python.lua')
0 files changed, 0 insertions, 0 deletions