refactor: split up vim.deprecate into two functions
#28836
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dundargoc
force-pushed
the
refactor/deprecate-split
branch
from
9d3b599
to
4732420
Compare
`vim.deprecate` has become too complicated, and the usecase for a general deprecation function that plugins can use vs a deprecation function that fits neovim's growing needs is becoming too different.
dundargoc
force-pushed
the
refactor/deprecate-split
branch
from
4732420
to
0ac874a
Compare
github-actions
bot
requested review from
bfredl,
clason,
gpanders,
lewis6991,
MariaSolOs,
mfussenegger and
wookayin
|
I'll incorporate these changes directly to #28778, that way it'll be easier to see if this is needed. |
github-actions
bot
removed request for
mfussenegger,
wookayin,
bfredl,
clason,
lewis6991,
gpanders and
MariaSolOs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
vim.deprecatehas become too complicated, and the usecase for ageneral deprecation function that plugins can use vs a deprecation
function that fits neovim's growing needs is becoming too different.