Summary: Now the users configuration and the default configuration is separated. This will make it easier to setup ivy with some defaults. Right now we only have the backends configurable however, it looks like we will be making other components of ivy configurable. To use this you can now call `ivy.setup` with no parameters and you will get the default config. You can also call it with a partial config and if the option is not found in the users config it will fallback to the users config value. Test Plan: Manual testing and with unit tests in CI
27 lines
878 B
Lua
27 lines
878 B
Lua
local config = require "ivy.config"
|
|
|
|
describe("config", function()
|
|
before_each(function()
|
|
config.user_config = {}
|
|
end)
|
|
|
|
it("gets the first item when there is only default values", function()
|
|
local first_backend = config:get { "backends", 1 }
|
|
assert.is_equal("ivy.backends.buffers", first_backend)
|
|
end)
|
|
|
|
it("returns nil if we access a key that is not a valid config item", function()
|
|
assert.is_nil(config:get { "not", "a", "thing" })
|
|
end)
|
|
|
|
it("returns the users overridden config value", function()
|
|
config.user_config = { backends = { "ivy.my.backend" } }
|
|
local first_backend = config:get { "backends", 1 }
|
|
assert.is_equal("ivy.my.backend", first_backend)
|
|
end)
|
|
|
|
it("returns a nested value", function()
|
|
config.user_config = { some = { nested = "value" } }
|
|
assert.is_equal(config:get { "some", "nested" }, "value")
|
|
end)
|
|
end)
|