Compare commits

...

2 commits

Author SHA1 Message Date
386e972834 ci: use GI_TOKEN so we can run ci on other platforms
Some checks failed
CI / Luacheck (pull_request) Successful in 23s
CI / Cargo Format (pull_request) Successful in 18s
CI / Build and test (pull_request) Successful in 1m53s
Conventional Tools Commitlint / Commitlint (pull_request) Successful in 5s
CI / StyLua (pull_request) Failing after 3s
Summary:

Starting to have a play with forgejo, on this platform you cannot define
secrets that have a prefix of `GITHUB_`. I still want to maintain CI on github
for any pull requests that may come in.

The plan in to use the `GITHUB_TOKEN` when we are running on github and use the
`GH_TOKEN` when we are running on forgejo

Test Plan:

Run the CI on github and forgejo, this will need to be a manual process to
validate this works.
2024-09-03 17:32:04 +01:00
8a7d510cda chore: make public api consistent
Some checks failed
CI / Luacheck (pull_request) Successful in 22s
CI / StyLua (pull_request) Failing after 4s
CI / Cargo Format (pull_request) Successful in 18s
CI / Build and test (pull_request) Successful in 1m50s
Conventional Tools Commitlint / Commitlint (pull_request) Successful in 5s
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-09-03 16:41:39 +01:00
4 changed files with 21 additions and 5 deletions

View file

@ -31,7 +31,7 @@ jobs:
- name: Run stylua
uses: JohnnyMorganz/stylua-action@v4.0.0
with:
token: ${{ secrets.GITHUB_TOKEN }}
token: ${{ secrets.GITHUB_TOKEN || secrets.GH_TOKEN }}
version: latest
args: --check .

View file

@ -3,7 +3,6 @@ local prompt = require "ivy.prompt"
local utils = require "ivy.utils"
local controller = {}
controller.action = utils.actions
controller.items = nil
controller.callback = nil
@ -56,7 +55,7 @@ end
controller.checkpoint = function()
vim.api.nvim_set_current_win(window.origin)
controller.callback(window.get_current_selection(), controller.action.CHECKPOINT)
controller.callback(window.get_current_selection(), utils.actions.CHECKPOINT)
vim.api.nvim_set_current_win(window.window)
end

View file

@ -1,11 +1,28 @@
local controller = require "ivy.controller"
local libivy = require "ivy.libivy"
local config = require "ivy.config"
local utils = require "ivy.utils"
local register_backend = require "ivy.register_backend"
local ivy = {}
ivy.action = utils.actions
ivy.utils = utils
ivy.match = libivy.ivy_match
ivy.run = controller.run
ivy.register_backend = register_backend
ivy.checkpoint = controller.checkpoint
ivy.paste = controller.paste
ivy.complete = controller.complete
ivy.destroy = controller.destroy
ivy.input = controller.input
ivy.next = controller.next
ivy.previous = controller.previous
ivy.search = controller.search
-- Private variable to check if ivy has been setup, this is to prevent multiple
-- setups of ivy. This is only exposed for testing purposes.
---@private

View file

@ -1,9 +1,9 @@
local controller = require "ivy.controller"
local api = require "ivy"
-- Put the controller in to the vim global so we can access it in mappings
-- better without requires. You can call controller commands like `vim.ivy.xxx`.
-- luacheck: ignore
vim.ivy = controller
vim.ivy = api
vim.paste = (function(overridden)
return function(lines, phase)