VCC Better feedback on migration failure
complete
Code-Floof
Currently during a failure there is no indication of what the error was. The button Delete It is also ambiguous and doesnt indicate if its referring to the Original Project / Cloned Project.
Log In
Fax
complete
Thank you for the request!
Version 2.0 of the Creator Companion adds a log with more detailed information about the migration process.
If you'd like to see additional improvements to the Creator Companion, please let us know by submitting a report.
Momo the Monster
in progress
In the new version 0.2.7, we've updated the messaging this way:
Migration Finished With Errors. What do you want to do with the new Migrated Project?
Open it to Investigate
Delete the new project
Does that clarify things?
Synergiance
Momo the Monster: It would be nice to have a "Do nothing" button to manually investigate before opening the project
s
savitsme
i used the update without copy option and got a error like this as well - from just that message its very unclear of if its actually a good idea to open the project due to, as it mentions in the usual updating docs that parts of the sdk are volatile, this feels like not enough information is given so that one can make an informed decision of how to proceed. in my case opening the project had lead to broken references. ultimately needing to restore from backup. (git didnt like that one apparently either)
i have to second floof here in that the delete button is way too ambigous, from the ui - does it delete the entire project? does it delete the packages it just imported again? maybe to prepare for reverting by say using the seperate project path of updating/replacing the sdk?
- displaying the kind of error that was detected would propably help a lot with this part.
- as well as clarifying in the delete it button if it is the project, or the package, or other things.
-- (if one even wants to do that, especially with the migration in place option as if it deletes the project this can also delete the git files)
- the addition of a close/display log files button might also be helpful.
Momo the Monster
interested
Momo the Monster
Merged in a post:
[FEEDBACK, 0.2.0] Allow users to view errors when migration fails before making a decision.
Synergiance
There should be either a "view log" or "show errors" button on this screen, so people can see what errors occurred before making a decision on whether to open a project or delete it. In this case, the project was safe to open and had non consequential errors.
Momo the Monster
Synergiance
Its relating to the cloned project (the one it attempted to convert) but I see your point, this should be better indicated.