From ae7698f4fe9a054c2427a8f5612422c9d6426b74 Mon Sep 17 00:00:00 2001 From: "Justin M. Keyes" Date: Wed, 2 Oct 2024 02:50:41 -0700 Subject: feat: expose config definition as `config_def` #3335 Problem: Users/plugins may want to use the config definition without actually activating the config via setup(). Solution: - Expose `config_def` field and document it. - Also undeprecate some stuff that doesn't yet have a documented alternative. TODO: configs.lua sets `M.filetypes = config.filetypes` and other fields in ad-hoc fashion "for :LspInfo" but it's not clear when those fields are actually populated, and they don't source from `config_def`... --- scripts/docgen.lua | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'scripts/docgen.lua') diff --git a/scripts/docgen.lua b/scripts/docgen.lua index 1a9328c4..e2749ba9 100644 --- a/scripts/docgen.lua +++ b/scripts/docgen.lua @@ -103,7 +103,7 @@ local function make_lsp_sections() 0, '\n', sorted_map_table(configs, function(template_name, template_object) - local template_def = template_object.document_config + local template_def = template_object.config_def local docs = template_def.docs local params = { -- cgit v1.2.3-70-g09d2