Search Issue Tracker
Won't Fix
Votes
1
Found in
2018.4
2019.4
2020.2.1f1
2020.3
2021.1
2021.2
Issue ID
1319087
Regression
No
UnityYAMLMerge does not respect EditorSettings.serializeInlineMappingsOnOneLine
How to reproduce:
1. Extract the attached project named "BUG_YamlMerge.zip"
2. Open SceneLeft.unity with a text editor (Located in the Assets folder)
3. Observe that line 133 is written in a single line
4. Open CMD in the current folder and execute the following command - "PATH_TO_THE_EDITOR_FOLDER\Editor\Data\Tools\UnityYAMLMerge.exe" merge -p SceneLeft.unity SceneLeft.unity SceneLeft.unity out.unity
5. Open the result file "out.unity" using a text editor
6. Observe line 133 once more
Expected results: The two merged files are the same. UnityYAMLMerge should not change the file if the files are the same
Actual results: The original line 133 is split into two separate lines
Reproducible with: 2018.4.35f1, 2019.4.26f1, 2020.3.8f1, 2021.1.7f1, 2021.2.0a17
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- A 404 page is opened when selecting "Open Documentation" on the Float Node in Shader Graph
- Shader Graph Importer's Documentation Reference button leads to a 404 page
- Crash on WriteParticleLineVertex when particle systems are rendered in a specific project
- Asset names longer than the allowed system file path are not handled gracefully
- Moving VFX Particles leave a ghosting trial in Ray Traced Screen Space Reflections
Resolution Note:
Although it is accurate that YAMLMerge does not support EditorSettings.serializeInlineMappingsOnOneLine, the effects are non-damaging and this issue does not meet the current level of severity required to resource and backport a fix for this.