Description

Here we force reimport all assets into Unity 2022.3 LTS with the means of this script:

using UnityEditor;using UnityEngine;using System.IO;public class ForceReserializeWindow : EditorWindow{    [MenuItem("Tools/Force Reserialize All Assets")]    public static void ShowWindow()    {        GetWindow<ForceReserializeWindow>("Force Reserialize Assets");    }    void OnGUI()    {        GUILayout.Label("Force all assets to be re-saved (reserialized).", EditorStyles.wordWrappedLabel);        if (GUILayout.Button("Force Reserialize All Assets"))        {            ForceReserializeAllAssets();        }    }    private static void ForceReserializeAllAssets()    {        // Get all asset paths in the project        string[] allAssetPaths = AssetDatabase.GetAllAssetPaths();                // Use ForceReserializeAssets with the option to reserialize both assets and metadata        // This loads, upgrades, and writes all data back to disk.        AssetDatabase.ForceReserializeAssets(allAssetPaths, ForceReserializeAssetsOptions.ReserializeAssetsAndMetadata);        Debug.Log($"Reserialization complete for {allAssetPaths.Length} assets.");    }}

This is done so that what we have on disk is actually 22.3 LTS data and not old data that is still usable due to compatibility paths. One of the benefits of this work is that with it landing, we won't get extra large diffs from doing seemingly small changes.

Testing status & QA

Local testing by dev.

Overall Product Risks

• Complexity: Low
• Halo Effect: Low

Checklist

Before review:

• Changelog entry added.
  • Explains the change inChanged,Fixed,Added sections.
  • For API change contains an example snippet and/or migration example.
  • JIRA ticket linked, example (case %%). If it is a private issue, just add the case ID without a link.
  • Jira port for the next release set as "Resolved".
• Tests added/changed, if applicable.
  • Functional testsArea_CanDoX,Area_CanDoX_EvenIfYIsTheCase,Area_WhenIDoX_AndYHappens_ThisIsTheResult.
  • Performance tests.
  • Integration tests.
• Docs for new/changed API's.
  • Xmldoc cross references are set correctly.
  • Added explanation how the API works.
  • Usage code examples added.
  • The manual is updated, if needed.

During merge:

• Commit message for squash-merge is prefixed with one of the list:
  • NEW: ___.
  • FIX: ___.
  • DOCS: ___.
  • CHANGE: ___.
  • RELEASE: 1.1.0-preview.3.