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
Right now aragon.js just swallows up failures to load or parse these files and tries to give back as much info as it can (just the on-chain info if both files failed to load).
Ideally, aragon.js would do this, but also capture the files that failed, or set a flag in the app instance, so that frontends can display an error state to the user.
Changes to apm.js are likely also needed...
The text was updated successfully, but these errors were encountered:
sohkai
changed the title
[wrapper] Emit an error if an app's manifest or artifact.json could not be loaded
[Wrapper] Emit an error if an app's manifest or artifact.json could not be loaded
Jan 14, 2019
sohkai
changed the title
[Wrapper] Emit an error if an app's manifest or artifact.json could not be loaded
[Wrapper] Emit an error if an app's manifest or artifact.json could not be loaded or parsed
Jan 14, 2019
sohkai
changed the title
[Wrapper] Emit an error if an app's manifest or artifact.json could not be loaded or parsed
Wrapper: emit an error if an app's manifest or artifact.json could not be loaded or parsed
Jan 14, 2019
Right now aragon.js just swallows up failures to load or parse these files and tries to give back as much info as it can (just the on-chain info if both files failed to load).
Ideally, aragon.js would do this, but also capture the files that failed, or set a flag in the app instance, so that frontends can display an error state to the user.
Changes to apm.js are likely also needed...
The text was updated successfully, but these errors were encountered: