You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been trying to make my own external adapter based off an example in this repo, but I've been having some issues because all the pieces of code I need are coupled to the yarn workspace. It's not very clear what is the minimum necessary of code that I need to get from this repo in order to make it work in another alone.
The text was updated successfully, but these errors were encountered:
Hi Pedro, I definitely agree that it's difficult to decouple EAs from the monorepo. The short answer is that for now it's easiest to just fork the monorepo as-is and create your adapter in it without trying to decouple it. With a bit more effort, you could remove all other unused adapters from the repo, but this will be tedious work with little reward.
To completely decouple your EA from the monorepo, I'd recommend waiting for EA framework v3. It's currently in a private beta, but we hope to publish it publicly soon. This will be a completely decoupled package without having to worry about yarn workspaces if you want to build your own adapter.
I will keep this issue open until v3 is released, in addition to any guides on how to build an EA in v3.
I've been trying to make my own external adapter based off an example in this repo, but I've been having some issues because all the pieces of code I need are coupled to the yarn workspace. It's not very clear what is the minimum necessary of code that I need to get from this repo in order to make it work in another alone.
The text was updated successfully, but these errors were encountered: