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
sample contract style could be better, e.g. Map.lookup_default instead of switching, removing unused return values (create_nested_map_if_not_exists), _variable syntax instead of 'variable also not needed in all cases, get_todo should not created a empty todo, why have a get_caller function
the sample vue project advertises putting a private key in the frontend, I don't find this a suitable example, to help people build on aeternity we should advertise using the Aepp() injection approach, e.g. by including the sample identity provider in the example.
in the sample I find returnType !== '()' missleading, I don't think an abstraction for calling should be needed, why does onCallStatic use manual decode-type instead of relying on the aci and contractInstance? Also onCallStatic doesn't to a static call if I see correct, anyways why the on naming semantic?
The text was updated successfully, but these errors were encountered:
Map.lookup_default
instead of switching, removing unused return values (create_nested_map_if_not_exists
),_variable
syntax instead of'variable
also not needed in all cases,get_todo
should not created a empty todo, why have aget_caller
functionAepp()
injection approach, e.g. by including the sample identity provider in the example.returnType !== '()'
missleading, I don't think an abstraction for calling should be needed, why doesonCallStatic
use manual decode-type instead of relying on the aci and contractInstance? AlsoonCallStatic
doesn't to a static call if I see correct, anyways why theon
naming semantic?The text was updated successfully, but these errors were encountered: