Best practices in naming and defining procedures when they don't fit into standard buckets?
I am loving TRPC and its type safety, but I feel like I'm struggling with the naming of procedures. I'm pretty confused with why I need to fit my procedures into one of the 3 buckets: query, mutation, or subscription. For example, I have
I felt inclined to define
I wanted the client code to read:
I'm fine with it if I can just have
Instead I have redundancy in the naming:
To make things more confusing, some procedures just don't fit into these buckets. I can have procedures which read nothing, write nothing, but perform some action like open a file in vscode. None of the above conventions work in this case.
My expectation when using it was simply to have an execute call, and let the author decide their naming conventions. If there is nothing special about a query or mutation, why introduce weird things that mess with the naming conventions and don't work in every case?
itemsI felt inclined to define
itemspublicProceduregetItemsupdateItemssubscribeToItemsI wanted the client code to read:
client.items.query()client.items.mutate(...)I'm fine with it if I can just have
client.getItems()client.updateItems(...)Instead I have redundancy in the naming:
client.getItems.query()client.updateItems.mutate(...)To make things more confusing, some procedures just don't fit into these buckets. I can have procedures which read nothing, write nothing, but perform some action like open a file in vscode. None of the above conventions work in this case.
My expectation when using it was simply to have an execute call, and let the author decide their naming conventions. If there is nothing special about a query or mutation, why introduce weird things that mess with the naming conventions and don't work in every case?
