When loading the plugin from a plugin manager the themes setup function would apply both configuration and the theme itself. This doesn't seem to be the case for many other popular colorschemes where only default/user configuration is applied on setup allowing the user to choose when to enable the colorscheme via colorscheme {theme} or require('theme').load(style).
While applying these changes there were a few other things I modified.
Allow style to be set from setup table and fallback to vim.o.background.
Replace functionally for vscode.change_style to vscode.load.
Basically simplifies the plugins api.
Rename colorscheme entrypoint file colors/vscode.vim to lua.
This doesn't change anything but appeals to my dislike of vimscript.
Much older versions of neovim might not support directly loading lua runtime files.
When loading the plugin from a plugin manager the themes setup function would apply both configuration and the theme itself. This doesn't seem to be the case for many other popular colorschemes where only default/user configuration is applied on setup allowing the user to choose when to enable the colorscheme via
colorscheme {theme}orrequire('theme').load(style).While applying these changes there were a few other things I modified.
Allow style to be set from setup table and fallback to
vim.o.background.Replace functionally for
vscode.change_styletovscode.load. Basically simplifies the plugins api.Rename colorscheme entrypoint file
colors/vscode.vimto lua. This doesn't change anything but appeals to my dislike of vimscript. Much older versions of neovim might not support directly loading lua runtime files.