This PR creates the project structure required for harpc on the typescript side and moves the rust client from harpc/client to harpc/client/rust.
I am not a huge fan of how much this nests harpc rust client, but I wasn't able to find a better way to do. You could imagine a harpc/bindings folder, but that wouldn't really be proper as well. We can always move it if we find a better structure.
Pre-Merge Checklist 🚀
🚢 Has this modified a publishable library?
This PR:
[x] does not modify any publishable blocks or libraries, or modifications do not need publishing
📜 Does this require a change to the docs?
The changes in this PR:
[x] are internal and do not require a docs change
🕸️ Does this require a change to the Turbo Graph?
The changes in this PR:
[x] affected the execution graph, and the turbo.json's have been updated to reflect this
🌟 What is the purpose of this PR?
This PR creates the project structure required for
harpc
on the typescript side and moves the rust client fromharpc/client
toharpc/client/rust
.Pre-Merge Checklist 🚀
🚢 Has this modified a publishable library?
This PR:
📜 Does this require a change to the docs?
The changes in this PR:
🕸️ Does this require a change to the Turbo Graph?
The changes in this PR:
turbo.json
's have been updated to reflect this