Is possible suppress 'deprecated' warning ?

[leonel-carrizo]

I hate this warning being showed every time I open my vault.
I am not using client. on my configuration.
I do believe is related how Lazy.vim pass the setting to obsidian.vim.
My settings are passed by opts {}

I already tried even removing some part of the configuration.
I already tried using require("obsidian").setup{} way to do it to avoid using opts option.

return {
	"obsidian-nvim/obsidian.nvim",
	event = "VeryLazy",
	version = "*", -- recommended, use latest release instead of latest commit
	lazy = true,
	ft = "markdown",
	-- README: https://github.com/obsidian-nvim/obsidian.nvim?tab=readme-ov-file#configuration-options
	opts = {
		workspaces = {
			{
				name = "Home",
				path = set_path(),
			},
		},
		notes_subdir = "00 Inbox",

		new_notes_location = "notes_subdir",

		disable_frontmatter = false,
		---@return table
		note_frontmatter_func = function(note)
			-- Add the title of the note as an alias.
			if note.title then
				note:add_alias(note.title)
			end
			if note.id == note.title or note.id == nil then
				note.id = tostring(os.date("%a%d%b%Y%H%M", os.time()))
			end
			local date = os.date("%d-%m-%Y %H:%M:%S", os.time())
			local out = { id = note.id, date = date, aliases = note.aliases, tags = note.tags }

			-- `note.metadata` contains any manually added fields in the frontmatter.
			-- So here we just make sure those fields are kept in the frontmatter.
			if note.metadata ~= nil and not vim.tbl_isempty(note.metadata) then
				for k, v in pairs(note.metadata) do
					out[k] = v
				end
			end

			return out
		end,

		templates = {
			subdir = "03 Templates",
			date_format = "%d-%m-%Y",
			time_format = "%H:%M:%S",
		},

		-- Customize how note IDs are generated.
		-- return string DayMonthYeartime
		---@return string
		note_id_func = function()
			local dateFormatted = os.date("%a%d%b%Y%H%M", os.time())
			return tostring(dateFormatted)
		end,

		---@diagnostic disable: luadoc-miss-type-name, undefined-doc-name, undefined-doc-param
		---@param opts { path: string, label: string, id: string|integer|?, anchor: obsidian.note.HeaderAnchor|?, block: obsidian.note.Block|? }
		---@return string
		wiki_link_func = function(opts)
			local file_name = require("obsidian.note").fname(opts)
			return string.format("[[%s|%s]]", file_name, opts.label)
		end,

		-- If file name is not given, return <Note>_<4random_chars>
		---@param spec { id: string, dir: obsidian.Path, title: string|? }
		---@return string|obsidian.Path The full path to the new note.
		note_path_func = function(spec)
			local filename = ""
			if spec.title ~= nil then
				local clean_title = spec.title:gsub(" ", "_"):gsub("[^A-Za-z0-9-]", "_")
				filename = clean_title
			else
				local random_chars = ""
				for _ = 1, 4 do
					random_chars = random_chars .. string.char(math.random(65, 90))
				end
				filename = "Note" .. "_" .. random_chars .. "_" .. tostring(spec.id)
			end
			local path = spec.dir / filename
			return path:with_suffix ".md"
		end,

		-- Customize behavior when use `:ObsidianFollowLink` on a link to an external
		---@param url string
		follow_url_func = function(url)
			-- Open the URL in the default web browser.
			vim.fn.jobstart { "open", url } -- Mac OS
			-- vim.fn.jobstart({"xdg-open", url})  -- linux
			-- vim.cmd(':silent exec "!start ' .. url .. '"') -- Windows
			-- vim.ui.open(url) -- need Neovim 0.10.0+
		end,

		image_name_func = function()
			local dateFormatted = os.date("%a%d%b%Y%H%M", os.time())
			return "Img" .. dateFormatted
		end,

		attachments = {
			img_folder = "02 Archive/Files_Assets",

			img_text_func = function(client, path)
				path = client:vault_relative_path(path) or path
				-- local name_no_ext = path.stem
				-- local extracted_part = name_no_ext:match(".*_(.*)")
				return string.format("![[./%s]]", path) -- Easier compatibility with image.nvim
			end,
		},
		legacy_commands = false,

	},
}

[neo451]

Client.opts is not the related to lazy's opts field which is a shorthand for .setups.
Client.opts is the old way of storing the options passed in and normalized by the setup function.
Since we are #237 so the options values is in the Obsidian global variable now.

You config looks fine, (apart from client:vault_relative_path is also not there anymore, use Path.vault_relative_path). Maybe you have other custom stuff not shown here, like the set_path function in workspace or somewhere else, that uses stuff like require"obsidian".get_client().opts, that is the one causing the warning.

[leonel-carrizo]

Thank you so much neo451 for your answer.
I will change the valult_relative_path thing

You're right, I'm using require"obsidian".get_client().opts on render-markdown plugin in order to shutdown the obsidian ui and give this responsibility to this plugin.

	config = function(_, opts)
			require("obsidian").get_client().opts.ui.enable = false
			-- vim.api.nvim_buf_clear_namespace(0, vim.api.nvim_get_namespaces()["ObsidianUI"], 0, -1)
			require("render-markdown").setup(opts)
		end,

What would be the new way to achieve this, if not too much ask.

[neo451]

	config = function(_, opts)
			Obsidian.opts.ui.enable = false
			-- vim.api.nvim_buf_clear_namespace(0, vim.api.nvim_get_namespaces()["ObsidianUI"], 0, -1)
			require("render-markdown").setup(opts)
		end,

is the new way to access the value. It looks like Snacks or Mini global vars if you are familiar with those.

But your usage has issues:

First you should just disable the ui module in

require"obsidian".setup{
   ui = { enable = false }
}

the reason is that the all the config values are read in different points of the setup, and plus the lazy loading stuff in lazy, I don't know when render-markdown's config block is going to be called, maybe before you call it, the old default value is already being read and registered the ui stuff. ui is just one example, if this works I am not surprised, but you can not use this pattern for all the config values in the codebase.

the purpose of the Obsidian.opts is to read the values that are passed in and normalized by the setup function, and workspace_override tables. So that if you have a custom script, you can reference the correct value you have set. So in short it should be read-only.

So I will make the table read-only and produce error in the future if users modify it by way of global var.