Merge branch 'rust-fetch-functions' of https://github.com/wjthieme/kinobi into rust-fetch-functions

Author: wjthieme

.eslintrc.js

@@ -32,6 +32,9 @@ jobs:
       - name: Install dependencies
         run: pnpm install --frozen-lockfile
 
+      - name: Compile JS and types
+        run: pnpm run build
+
       - name: Check linting
         run: pnpm run lint
 
@@ -101,3 +104,22 @@ jobs:
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
+
+  dependabot:
+    runs-on: ubuntu-latest
+    if: github.event_name == 'pull_request' && github.event.pull_request.user.login == 'dependabot[bot]' && github.repository == 'codama-idl/codama'
+    needs: [lint, tests]
+    permissions:
+      contents: write
+      pull-requests: write
+    steps:
+      - name: Auto-approve the PR
+        run: gh pr review --approve "$PR_URL"
+        env:
+          PR_URL: ${{ github.event.pull_request.html_url }}
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      - name: Enable auto-merge
+        run: gh pr merge --auto --squash "$PR_URL"
+        env:
+          PR_URL: ${{ github.event.pull_request.html_url }}
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/main.yml

@@ -31,8 +31,8 @@ Because everything is designed as a `Node`, we can transform the IDL, aggregate
 
 There are various ways to extract information from your Solana programs in order to obtain a Codama IDL.
 
--   **Using Codama macros**. This is not yet available but you will soon have access to a set of Rust macros that help attach IDL information directly within your Rust code. These macros enable Codama IDLs to be generated whenever you build your programs.
--   **From Anchor IDLs**. If you are using [Anchor programs](https://github.com/coral-xyz/anchor) or [Shank macros](https://github.com/metaplex-foundation/shank), then you can get an Anchor IDL from them. You can then use the `@codama/nodes-from-anchor` package to convert that IDL into a Codama IDL as shown in the code snippet below. Note that the Anchor IDL might not offer all the information that Codama can hold and therefore, you may want to transform your Codama IDL to provide additional information. You can learn more about this in the next section.
+- **Using Codama macros**. This is not yet available but you will soon have access to a set of Rust macros that help attach IDL information directly within your Rust code. These macros enable Codama IDLs to be generated whenever you build your programs.
+- **From Anchor IDLs**. If you are using [Anchor programs](https://github.com/coral-xyz/anchor) or [Shank macros](https://github.com/metaplex-foundation/shank), then you can get an Anchor IDL from them. You can then use the `@codama/nodes-from-anchor` package to convert that IDL into a Codama IDL as shown in the code snippet below. Note that the Anchor IDL might not offer all the information that Codama can hold and therefore, you may want to transform your Codama IDL to provide additional information. You can learn more about this in the next section.
 
     ```ts
     import { createFromRoot } from 'codama';
@@ -42,7 +42,7 @@ There are various ways to extract information from your Solana programs in order
     const codama = createFromRoot(rootNodeFromAnchor(anchorIdl));
     ```
 
--   **By hand**. If your Solana program cannot be updated to use Codama macros and you don’t have an Anchor IDL, you may design your Codama IDL by hand. We may provide tools such as a Codama Playground to help with that in the future.
+- **By hand**. If your Solana program cannot be updated to use Codama macros and you don’t have an Anchor IDL, you may design your Codama IDL by hand. We may provide tools such as a Codama Playground to help with that in the future.
 
 ## Transforming Codama
 
@@ -61,12 +61,12 @@ Now that you have the perfect Codama IDL for your Solana program, you can benefi
 
 _Note that some features such as rendering CLIs are not yet available. However, because the Codama IDL is designed as a tree of nodes, these features are only a visitor away from being ready. Feel free to reach out if you’d like to contribute to this Codama ecosystem._
 
--   **Rendering client code**. Want people to start interacting with your Solana program? You can use special visitors that go through your Codama IDL and generate client code that you can then publish for your end-users. Currently, we have the following renderers available:
+- **Rendering client code**. Want people to start interacting with your Solana program? You can use special visitors that go through your Codama IDL and generate client code that you can then publish for your end-users. Currently, we have the following renderers available:
 
-    -   `@codama/renderers-js`: Renders a JavaScript client compatible with the soon-to-be-released 2.0 line of [`@solana/web3.js`](https://github.com/solana-labs/solana-web3.js).
-    -   `@codama/renderers-js-umi`: Renders a JavaScript client compatible with Metaplex’s [Umi](https://github.com/metaplex-foundation/umi) framework.
-    -   `@codama/renderers-rust`: Renders a Rust client that removes the need for publishing the program crate and offers a better developer experience.
-    -   _And more to come._
+    - `@codama/renderers-js`: Renders a JavaScript client compatible with the soon-to-be-released 2.0 line of [`@solana/web3.js`](https://github.com/solana-labs/solana-web3.js).
+    - `@codama/renderers-js-umi`: Renders a JavaScript client compatible with Metaplex’s [Umi](https://github.com/metaplex-foundation/umi) framework.
+    - `@codama/renderers-rust`: Renders a Rust client that removes the need for publishing the program crate and offers a better developer experience.
+    - _And more to come._
 
     Here’s an example of how to generate JavaScript and Rust client code for your program.
 
@@ -77,6 +77,6 @@ _Note that some features such as rendering CLIs are not yet available. However,
     codama.accept(renderRustVisitor('clients/rust/src/generated', { ... }));
     ```
 
--   **Registering your Codama IDL on-chain** (_Coming soon_). Perhaps the biggest benefit of having a Codama IDL from your program is that you can share it on-chain with the rest of the ecosystem. This means explorers may now use this information to provide a better experience for users of your programs. Additionally, anyone can now grab your Codama IDL, select the portion they are interested in and benefit from the same ecosystem of Codama visitors to iterate over it. For instance, an app could decide to grab the IDLs of all programs they depend on, filter out the accounts and instructions they don’t need and generate a bespoke client for their app that only contains the functions the app needs.
--   **Rendering CLIs** (_Not yet available_). Whilst not available yet, we can imagine a set of CLI commands that can be generated from our Codama IDL (much like our clients) so that end-users can fetch decoded accounts and send instructions directly from their terminal.
--   **Rendering documentation** (_Not yet available_). Similarly to CLIs, we may easily generate documentation in various formats from the information held by our Codama IDL.
+- **Registering your Codama IDL on-chain** (_Coming soon_). Perhaps the biggest benefit of having a Codama IDL from your program is that you can share it on-chain with the rest of the ecosystem. This means explorers may now use this information to provide a better experience for users of your programs. Additionally, anyone can now grab your Codama IDL, select the portion they are interested in and benefit from the same ecosystem of Codama visitors to iterate over it. For instance, an app could decide to grab the IDLs of all programs they depend on, filter out the accounts and instructions they don’t need and generate a bespoke client for their app that only contains the functions the app needs.
+- **Rendering CLIs** (_Not yet available_). Whilst not available yet, we can imagine a set of CLI commands that can be generated from our Codama IDL (much like our clients) so that end-users can fetch decoded accounts and send instructions directly from their terminal.
+- **Rendering documentation** (_Not yet available_). Similarly to CLIs, we may easily generate documentation in various formats from the information held by our Codama IDL.

README.md

@@ -0,0 +1,17 @@
+import solanaConfig from '@solana/eslint-config-solana';
+import tseslint from 'typescript-eslint';
+
+export default tseslint.config([
+    {
+        files: ['**/*.ts', '**/*.(c|m)?js'],
+        ignores: ['**/dist/**', '**/e2e/**'],
+        extends: [solanaConfig],
+    },
+    {
+        files: ['packages/nodes/**', 'packages/node-types/**'],
+        rules: {
+            'sort-keys-fix/sort-keys-fix': 'off',
+            'typescript-sort-keys/interface': 'off',
+        },
+    },
+]);

eslint.config.mjs

@@ -13,27 +13,28 @@
     },
     "devDependencies": {
         "@changesets/changelog-github": "^0.5.0",
-        "@changesets/cli": "^2.27.9",
+        "@changesets/cli": "^2.27.11",
         "@codama/internals": "workspace:*",
-        "@solana/eslint-config-solana": "^3.0.3",
+        "@eslint/js": "^9.17.0",
+        "@eslint/json": "^0.9.0",
+        "@solana/eslint-config-solana": "^4.0.0",
         "@solana/prettier-config-solana": "0.0.5",
-        "@types/node": "^20",
-        "@typescript-eslint/eslint-plugin": "^6.21.0",
-        "@typescript-eslint/parser": "^6.0.0",
+        "@types/node": "^22",
+        "@typescript-eslint/eslint-plugin": "^8.19.1",
+        "@typescript-eslint/parser": "^8.19.1",
         "agadoo": "^3.0.0",
-        "eslint": "^8.57.1",
-        "eslint-config-turbo": "^2.2.3",
-        "eslint-plugin-simple-import-sort": "^10.0.0",
+        "eslint": "^9.17.0",
+        "eslint-plugin-simple-import-sort": "^12.1.1",
         "eslint-plugin-sort-keys-fix": "^1.1.2",
         "eslint-plugin-typescript-sort-keys": "^3.3.0",
-        "happy-dom": "^15.11.0",
-        "prettier": "^3.3.3",
+        "happy-dom": "^16.5.3",
+        "prettier": "^3.4.2",
         "rimraf": "6.0.1",
         "tsup": "^8.3.5",
-        "turbo": "^2.2.3",
-        "typescript": "^5.6.3",
-        "vitest": "^2.1.4",
-        "zx": "^8.2.0"
+        "turbo": "^2.3.3",
+        "typescript": "^5.7.3",
+        "vitest": "^2.1.8",
+        "zx": "^8.3.0"
     },
     "engines": {
         "node": ">=18.0.0"

package.json

@@ -1,6 +1,6 @@
 {
     "name": "@codama/dynamic-codecs",
-    "version": "1.1.0",
+    "version": "1.1.1",
     "description": "Get codecs on demand for Codama IDLs",
     "exports": {
         "types": "./dist/types/index.d.ts",

packages/dynamic-codecs/package.json

@@ -249,7 +249,7 @@ export function getNodeCodecVisitor(
             return transformCodec(
                 getMapCodec(key, value, { size }),
                 (value: object) => new Map(Object.entries(value)),
-                (map: Map<unknown, unknown>): object => Object.fromEntries(map),
+                (map: Map<unknown, unknown>) => Object.fromEntries(map) as object,
             ) as Codec<unknown>;
         },
         visitNumberType(node) {

packages/dynamic-codecs/src/codecs.ts

@@ -67,7 +67,7 @@ export function getValueNodeVisitor(
                     const value = visit(entry.value, this);
                     return [key, value];
                 }),
-            );
+            ) as unknown;
         },
         visitNoneValue() {
             return { __option: 'None' };

packages/dynamic-codecs/src/values.ts

@@ -1,6 +1,6 @@
 {
     "name": "@codama/dynamic-parsers",
-    "version": "1.1.0",
+    "version": "1.1.1",
     "description": "Helpers to dynamically identify and parse accounts and instructions",
     "exports": {
         "types": "./dist/types/index.d.ts",

packages/dynamic-parsers/package.json

@@ -53,7 +53,6 @@ export function parseInstruction(
 ): ParsedInstruction | undefined {
     const parsedData = parseInstructionData(root, instruction.data);
     if (!parsedData) return undefined;
-    instruction.accounts;
     const instructionNode = getLastNodeFromPath(parsedData.path);
     const accounts: ParsedInstructionAccounts = instructionNode.accounts.flatMap((account, index) => {
         const accountMeta = instruction.accounts[index];