Custom pin function

[awmuncy]

By default, JETI uses your local IPFS node and errors out if you don't have a remote pinning service connected. This meant you could only work with the "standardized" IPFS pinning API. But that isn't fully supported everywhere. So if you want to set up your own pin function, you can do that now, like so:

import { setup } from '@tableland/jeti';

setup({
   pin: async (content) => {
          let { cid } = pinContentToMyService(content);
          return {
              cid,
              pinned: true
         }
   }
)

prepare`INSERT INTO TABLE (id, name) values (5, '${new TextEncoder().encode("Hi there")}')`;

[carsonfarmer]

How robust is that prepare tooling? Should we move it into core js-tableland?

[awmuncy]

How robust is that prepare tooling? Should we move it into core js-tableland?

I think naming it "prepare" is a bit of a misnomer, and I think I'm going to rename it to "process". So probably not robust for the uses of which you're thinking.

Though in the next iteration maybe? I'm actually rethinking JETI's premise. "JavaScript Extension for Tableland and IPFS". Tableland queries with IPFS? Great! But really, it could be even better. And more simple. If we just use a custom process function and custom resolve function, both of which the user can specficy, we can make it "JavaScript Extension for Tableland Integrations" or something.
You can do something like

import { setup } from '@tableland/sdk';
setup({
   processor: (content) => {
        return await addContentToIpfsAndReturnCid(content);
   }
});

db.prepare(await process`INSERT INTO mytable (id, avatar) values ('1', ${avatar})`).run();

and the process tagged template could add it to IPFS. Alternatively, it could turn it to base64, or encrypt it, or... well, do anything you want.

Same concept with resolve, except it would be

// Custom resolve funtion
resolver(cell) {
     if(cell.column==="avatar") {
         return await resolveFromIpfs(cell.content);
     } 
     return cell.content;
}

// Elsewhere
resolve(db.prepare("SELECT id, name from table;").all());

[dtbuchholz]

(In general, I think this would be a nice feature as part of the SDK, too. Uploading data to IPFS and storing CIDs in tables is a core use case.)

The base branch was changed.

[joewagner]

Looks like my approval got wiped when I updated the staging branch. Approving again