-
-
Notifications
You must be signed in to change notification settings - Fork 198
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Announcements and Breaking Changes #387
Comments
Version 2.0.0 which is due to be merged in a few days, will change the required neovim version to 0.7.0 so this plugin can benefit from all the api changes and remove the Any user wanting to stay on the pre 0.7.0 version of this plugin should use the use {'akinsho/bufferline.nvim', tag = 'v1.*' } |
config = {
options = {
indicator = {
style = 'icon',
icon = '|',
}
}
} This will eventually be removed in a month |
All highlighting must now be done using the same arguments as are used for Please see This removes an old piece of legacy code that was manually translating user gui attributes into the correct format once this plugin migrated to This translation is scheduled for removal in 1 month as well. |
I've now automated releasing bufferline versions so will be removing the |
I'v deprecated options = {
get_element_icon = function(element)
return require('bufferline').get_element_icon(element.name, {default = true})
end
} |
I've also changed the options = {
groups = {
options = { toggle_hidden_on_enter = true },
items = {
{
name = 'Dependencies',
icon = '',
matcher = function(buf) -- buf here is now only a subset of the full buffer object
return vim.startswith(buf.path, vim.env.VIMRUNTIME)
end,
},
} This should not affect most people only anyone using one of the more obscure fields. If that was you please open an issue. If it's a very private field then we'll discuss if there's a way to replicate it and if not maybe it worth re-adding. |
Removed the old |
Hi 👋🏾,
If you want to know ahead of time about any changes or breakage, please subscribe to this issue. Generally I will now do all development on the
dev
branch which is unstable, so I have the freedom to try new things and develop quickly there without worrying about disrupting users workflows. This plugin will also use tags and semver, so users can pin their installations to the latest major version e.g.tag = 1.*
and only upgrade major version when they are ready to migrate.I will announce anything of note on this thread, so users are aware in advance.
The text was updated successfully, but these errors were encountered: