Allow Studio to migrate the new project #383
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Studio is currently unable to migrate a new project because the project.studio file does not exist in the new project archive. Furthermore, since the file does not exist, Studio creates the file and therefore uses the current version of the application.
No migration can therefore be carried out.
This PR allows Studio to update the project.studio file and retain the latest version of Studio used in the Technical Demo / new project archive. However, this feature is only functional if there is a project.studio in the archive, which is not the case with 1.0.7.
Note before testing
You need a specific version of the new project archive which contains the project.studio file:
https://mega.nz/file/h5pDQSzQ#EDGI4QkIrxTWbSZ0ntpoK7snUMn9f9uf6wyByIJFz_U
Copy the archive to the root of the Pokémon Studio project.
https://github.com/user-attachments/assets/2c16338d-e938-4150-ab1f-90ca3a010208
In the file
\src\backendTasks\checkDownloadNewProject.ts
, in the line 28, changeneedDownload: true
byneedDownload: false
.Tests to perform