Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
9
Found in
Issue ID
1119033
Regression
No
[ShaderGraph] FormerlySerializedAs do not works with JSon serialisation
When serializing element with JSonUtility, user should be able to migrate data using provided FormerlySerializedAs attribute as in Yaml.
Step to reproduce:
- Create a project with an old and new data structure with a field only changing by its name using the FormerlySerializedAs attribute. (check provided attached file that contain a test with this.)
- Try to save the old format in a json and then load it in the new structure format.
Expected: if FormerlySerializedAs refer to the old name, the deserialization should be able to retrieve the field value.
What can be seen: FormerlySerializedAs do nothing in case of JSon serialisation.
Note: ShaderGraph serialize the shaders in JSon format. Thus it is currently impossible to migrate data when we make shader upgrade.
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
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
- [Linux] Touch freezes in Player when any mouse button is clicked
- UnityEngine.Rendering.Volume.OnEnable() is called twice before OnDisable() creating multiple copies of the same volume when a volume is enabled right after Domain Reload when entering Play Mode
- Hinge Joint transforms are reset when toggling the "useMotor" property
- Motion Vector texture reports incorrect Mesh data when Mesh is coming from off-screen
Resolution Note:
We will look to improving JSON support, including FormerlySerializedAs as part of our ongoing feature development, and will continue to track this request internally.