chore: make public api consistent #1

Merged

AdeAttwood merged 1 commit from adeattwood/public-api into 0.x 2024-09-03 19:37:35 +00:00

Conversation 0 Commits 1 Files changed 3 +20 -4

AdeAttwood commented 2024-09-02 19:55:53 +00:00

Owner

Copy link

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.

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.

AdeAttwood added 1 commit 2024-09-02 19:55:54 +00:00

chore: make public api consistent ... ea6727db40

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.

AdeAttwood force-pushed adeattwood/public-api from ea6727db40 to c1ede21dd8 2024-09-03 06:47:07 +00:00 Compare

AdeAttwood force-pushed adeattwood/public-api from c1ede21dd8 to 8a7d510cda 2024-09-03 15:47:45 +00:00 Compare

AdeAttwood added 1 commit 2024-09-03 16:32:33 +00:00

ci: use GI_TOKEN so we can run ci on other platforms ... 386e972834

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.

AdeAttwood self-assigned this 2024-09-03 17:24:56 +00:00

AdeAttwood force-pushed adeattwood/public-api from 386e972834 to ded926a4a6 2024-09-03 18:34:53 +00:00 Compare

AdeAttwood merged commit ded926a4a6 into 0.x 2024-09-03 19:37:35 +00:00

AdeAttwood deleted branch adeattwood/public-api 2024-09-03 19:46:53 +00:00

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

AdeAttwood

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: AdeAttwood/ivy.nvim#1

No description provided.