feature: use data attribute in User events.

[aarondill]

Did you check the docs?

• I have read all the lazy.nvim docs

Is your feature request related to a problem? Please describe.

The docs list the available events, and only LazyLoad has anything set in the data attribute (the plugin name).

My personal use-case is to attempt to implement the hack you mentioned here to have documentation always loaded while lazy loading plugins.

Describe the solution you'd like

Other events where having information about which plugin will change/just changed include:
LazyInstall, LazyUpdate, LazyClean, LazyInstallPre, LazyUpdatePre, LazyCleanPre

Less immediately useful but potentially have a use-case:
LazyCheck: plugins for which updates were found
LazySync: which plugins changed (do we know this info?)
LazySyncPre: which plugins will change (impossible?)
LazyReload: which file(s) changed to cause the reload

Describe alternatives you've considered

• somehow diff the /lazy folder between LazyEventPre and LazyEvent
• Assume all plugins changed when LazyInstall, LazyUpdate, LazyClean or LazyCheck fire

Additional context

No response

[folke]

It's better to just use the unloaded rtp for showing helptags in telescope/fzf-lua.

Related: ibhagwan/fzf-lua#1296

[aarondill]

That is a better implementation of this specific use case, however this issue is about the generic implementation of Lazy's User events.
I have run into several instances where there was an existing event for what I wanted to hook into, but it didn't provide the information needed to do anything useful. For example, patching a plugin on Build/Install; notifying on installing incompatible dependencies; etc.

I don't expect lazy to implement my specific use cases, but i'd like for the event system to provide as much information as possible to user hooks.