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
cross-canister calls should also break, check those tests
Suppress esbuild warning/s
Still might want the explicit esbuild-tsconfig.json
js-sha256 might be showing issues with closures, I do not think we should need all of the global variable definitions that we are forced to use right now
To get js-sha256 to work it seems like we need to fork it or provide a lot of strange polyfills...consider our strategy with other packages moving forward. It might be best to just fork what we need to fork...that will give us the ultimate control that we need. Community members can maintain the forks and hopefully upstream their changes over time. For @dfinity/principal, we shouldn't have to change anything except for using esbuild's import injection thing (I'm hoping this is possible) to point to another package that has the expected interface...and perhaps the easiest thing to point to is a fork of js-sha256 called js-sha256-azle
Another idea is to mess with the module format in esbuild or swc, perhaps we can strip away a lot of the code in js-sha256 that is messing things up
Why isn't the management canister example breaking?
go remove all of the custom code that we don't need anymore, I think it will mostly be in azle/canisters/ledger/address
The context used to create the Principal must be the context used during AzleTryFromJsValue
Remove the AzleTryFromJsValue context code and run all tests again, might not need the weird hack?? Actually we need it because of the stable storage issue, yes I remember now
Make sure this works and that we have tests for it
The text was updated successfully, but these errors were encountered: