授权项目更改Authorizing project changes

在修改 Unity 项目之前,需要查看和批准对清单和项目文件所做的更改:Before modifying the Unity project, changes to the manifest and project files need to be reviewed and approved:

请求授权

file:///Manifest

可以在左侧的“清单”列中查看建议的清单更改。The proposed manifest changes can be viewed in the Manifest column on the left. 该内容与将写入项目清单 (Packages/manifest.json) 的内容完全相同:The contents are exactly what will be written to the project manifest (Packages/manifest.json):

清单预览

要复制到项目中的文件Files to be copied into the project

右侧的“要复制到项目中的文件”部分列出了将复制到 Unity 项目中的特定功能包文件:The Files to be copied into the project section on the right lists the specific feature package files that will be copied into the Unity project:

包含要复制的文件的清单预览

比较清单Compare manifests

可通过选择“比较”来查看所有建议更改的详细并排比较:You can see a detailed side-by-side comparison of all proposed changes by selecting Compare:

比较清单

批准更改Approving changes

建议的更改获得批准后,所列文件将被复制到 Unity 项目中,并将更新清单,使其包含对这些文件的引用。When the proposed changes are approved, the listed files will be copied into the Unity project and the manifest will be updated with references to these files.

备注

应将功能包 (*.tgz) 文件添加到源代码管理。The feature package (*.tgz) files should be added to source control. 它们使用相对路径进行引用,使开发团队能够轻松共享功能和清单更改。They are referenced using a relative path to enable development teams to easily share features and manifest changes.

在修改过程中,将对当前 manifest.json 文件进行备份。As part of the modifications, the current manifest.json file will be backed up.

重要

查看清单备份时,最早的备份将称为 manifest.json.backup。When viewing the manifest backups, the oldest will be called manifest.json.backup. 后续的新备份将使用从零 (0) 开始的数字值进行批注。Newer backups will be annotated with a numeric value, beginning with zero (0).

返回到上一步骤Going back to the previous step

如需对功能选择进行更改,请单击“返回”,返回到导入步骤。If you need to make changes to your feature selections, use Go Back to return to the import step.

另请参阅See also