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.
ci: run stylua via npx rather than via action
2024-09-03 19:34:17 +01:00 · 2024-09-03 19:20:09 +01:00
1 changed files with 1 additions and 5 deletions
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@ -29,11 +29,7 @@ jobs:
        uses: actions/checkout@v4
      - name: Run stylua
-        uses: JohnnyMorganz/stylua-action@v4.0.0
+        run: npx @johnnymorganz/stylua-bin --check .
        with:
          token: ${{ secrets.GITHUB_TOKEN || secrets.GH_TOKEN  }}
          version: latest
          args: --check .
  cargo-format:
    name: Cargo Format
Author	SHA1	Message	Date
Ade Attwood	ded926a4a6	chore: make public api consistent All checks were successful CI / Luacheck (pull_request) Successful in 20s Details CI / StyLua (pull_request) Successful in 12s Details CI / Cargo Format (pull_request) Successful in 18s Details CI / Build and test (pull_request) Successful in 2m2s Details Conventional Tools Commitlint / Commitlint (pull_request) Successful in 4s Details CI / Luacheck (push) Successful in 22s Details CI / StyLua (push) Successful in 12s Details CI / Cargo Format (push) Successful in 18s Details CI / Build and test (push) Successful in 1m52s Details Conventional Tools Commitlint / Commitlint (push) Successful in 5s Details 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 19:34:17 +01:00
Ade Attwood	f910955ad1	ci: run stylua via npx rather than via action All checks were successful CI / Luacheck (push) Successful in 22s Details CI / StyLua (push) Successful in 12s Details CI / Cargo Format (push) Successful in 19s Details CI / Build and test (push) Successful in 1m50s Details Conventional Tools Commitlint / Commitlint (push) Successful in 5s Details Summary: This is so we don't need the GITHUB_TOKEN that can not be added in forgejo. I am giving it a go and the `GITHUB_` prefix is reserved for secrets. There are also issues with the action in a forgejo environment due to the API not resolving to github. This now should work on both platforms. So we can maintain github compatibility for any pull requests that may come that way. Test Plan: Run the CI on github and forgejo, this will need to be a manual process to validate this works. Pull Request: #2	2024-09-03 19:20:09 +01:00