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
The native token package builder uses an hardcoded path to read a template file that is then copied into a temp folder for building a native token package.
This forces any built iota-genesis-builder bin to read from that hardcoded path. However, the template content could be simply saved as a constant.
Additionally, the template Move.toml references dependencies as local and points to the local path of the iota-framework. This could also be avoided and a reference to a specific framework version should be made.
The text was updated successfully, but these errors were encountered:
The native token package builder uses an hardcoded path to read a template file that is then copied into a temp folder for building a native token package.
This forces any built
iota-genesis-builder
bin to read from that hardcoded path. However, the template content could be simply saved as a constant.Additionally, the template
Move.toml
references dependencies aslocal
and points to the local path of the iota-framework. This could also be avoided and a reference to a specific framework version should be made.The text was updated successfully, but these errors were encountered: