Feat/workerize

[Keyrxng]

Resolves #92

[gentlementlegen]

@Keyrxng Since you switched to bun could you upgrade to the latest version and change the lockb to lock

[Keyrxng]

@Keyrxng Since you switched to bun could you upgrade to the latest version and change the lockb to lock

Done buddy ty for the review

[whilefoo]

this is still backward-compatible, right? just the function signature changed (no more context, just permit requests), so we can keep using it as a library until everything is ready

[Keyrxng]

Marked as off-topic because I was forward thinking things instead rather than for the npm package, my bad.

[Keyrxng]

PermitRequests previously sent username instead of user.id. We can either update the invoker or I can revert that change and fetch their GH ID?

This is the only important sentence to address before we can merge this and address the other problems in a separate PR

permit-generation/src/handlers/generate-payout-permit.ts

Line 17 in cb20e43

const { type, amount, username, contributionType, tokenAddress } = permitRequest;

this is still backward-compatible, right? just the function signature changed (no more context, just permit requests), so we can keep using it as a library until everything is ready

We could release a new major and we'd be safe no matter what I'm sure, I figured that's what we'd be doing.

[whilefoo]

PermitRequests previously sent username instead of user.id. We can either update the invoker or I can revert that change and fetch their GH ID?

I think user id and wallet address should be passed in because we already fetch wallet address in text-conversation-rewards so it doesn't make sense to do it twice. permit-generation should be minimalistic and only focus on generating permits

[Keyrxng]

I'm assuming you are talking about in regards to the npm package, but once permit generation is centralized to the worker I assume that it will be responsible for the user checks and pushing to the DB?

Kept userId and added userWalletAddress so we will need to update text-conversation.

I haven't touched the encode/decode methods or the types associated with them because that would break pay.ubq I'm sure so that can be left until the worker is rolled out.