Yes. In the YouTube video introducing the boilerplate, you mentioned that Example
can be safely removed/not imported while the others are required. However, at the moment this is not the case.
From the looks of it those contents should be in the DLLs
folder.
Apart from UniTask
, no, I added a bunch of asmdef
s myself because the code I work with uses them extensively.
Specifically, I added an asmdef
in each of these folders: Moralis
, WalletConnectSharp\WalletConnectSharp.Core
, WalletConnectSharp.Unity
.
I’m also aware of the one in the location you provided because I was linking each of these asmdef
s up that way.
EDIT: at the moment I’ve put an asmdef
at the root of the MoralisWeb3ApiSdk
folder and linked up the required inner asmdef
s correctly. For the purpose of my code, I can use this now, without modifying any of the scripts (except for deleting the duplicate script from WalletConnectSharp.Unity\EditorTools
– I prefer following the Unity convention of using Editor
instead).
My point was that WalletSelectItem
was being referenced by WalletConnectSharp.Unity
from Moralis
which doesn’t make sense from a modular standpoint.
I’m trying to make a UPM package for local use which incorporates the Moralis boilerplate minus the Example and its scenes (UPM does not support putting scenes in packages), with a bunch of asmdef
s for linking with the rest of my codebase.
Other Issues
BTW does the boilerplate package make changes to TextMeshPro? I see that it is included along with the rest of the package contents, which is expected because Unity packages all dependencies together.
I’m also seeing some .cs.bak
files in the project, unsure if that should be kept around?
Is it possible to currently work with IL2CPP with this project? I found this GitHub issue about not being able to find HttpUtility
when using .NET Framework 4.x.
I can make a pull request if you need it!