ivy.nvim/lua
Ade Attwood ea6727db40
Some checks failed
CI / Luacheck (pull_request) Successful in 1m2s
Conventional Tools Commitlint / Commitlint (pull_request) Successful in 35s
CI / Cargo Format (pull_request) Successful in 18s
CI / StyLua (pull_request) Failing after 4s
CI / Build and test (pull_request) Successful in 2m2s
chore: make public api consistent
Summary:

Right now we have two ways to access the public api we have `require('ivy')`
and `vim.ivy. Each way has a different api that will cause some confusion.

Now both apis are the same so anyone that wants to integrate with ivy can do so
without having to figure out what one they need to use.

Test Plan:

The unit tests cover most of the work, I have also been using this locally for
quite some time now with now issues.
2024-07-24 22:19:35 +01:00
..
ivy chore: make public api consistent 2024-07-24 22:19:35 +01:00