Thanks so much @frol ! do you have any opinions on parameters being passed into the functions? i.e you have:
nftMint({ token_id, metadata, receiver_id, perpetual_royalties }) {
but it could also be:
nftMint({ tokenId, metadata, receiverId, perpetualRoyalties }) {
I think anything public facing should be snake case as to promote interoperability but internal functions could take args as camel case. An example of this is the public facing function nft_mint I’ve defined here which has snake case args but it calls an internal method which takes camel case args as show here.

Oh, good catch! Well, parameters are easy to match in JS:

@call('nft_mint')
nftMint({ token_id: tokenId, metadata: metadata, receiver_id: receiverId, perpetual_royalties: perpetualRoyalties }) {
   ...
}

It is a bit verbose, but should be quite straightforward for JS folks

Though, nested parameters will become tedious to handle this way, so again, maybe consider some mapping. I love how serde in Rust allows one to #[serde(rename_all = "camelCase")]. Also given that we should validate the user input anyway, I would suggest we do some magic of automatic validation of the inputs using something like zod and then also remap (seems to only support through .transform at the moment) snake_case input fields to camelCase