feature: guidance request / documentation #1453
-
Did you check the docs?
Is your feature request related to a problem? Please describe.There is not a problem with lazy. I created a plugin and made a naming / namespace mistake, that I'd like to correct without breaking peoples installations. Describe the solution you'd likeI am looking for some guidance, how I could rename the module. My module has a github repo Is there some guidance available how to smoothly create deprecation notices and give people time to move their configs to the new naming scheme? Describe alternatives you've consideredI considered moving all the content to I am unsure, what the best way is within lazy to display things like that to the user. I saw that sometimes there are such notices in the Changelogs that lazy displays, but I could not find an info how to go about it. The events like If you have a pointer to best practices, I would highly appreciate it. If you don't have time for questions like this, I fully understand, then please close the issue. I just thought, maybe more are running into this kind of thing... Thanks in advance and apologies if this question is out of place... Michael. Additional contextNo response |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Used a message amendment, will later switch to |
Beta Was this translation helpful? Give feedback.
Used a message amendment, will later switch to
vim.deprecate()
calls.