Reply To: Feature Request: Save to JSON by default

Forums › 💬 NodeCanvas › 🗨️ General Discussion › Feature Request: Save to JSON by default › Reply To: Feature Request: Save to JSON by default

May 27, 2015 at 5:18 pm #14469
async0x42
Participant

    Pre-TLDR: Unity’s forced-text serialization YAML is really bad, and breaks imported assets without even telling you. If possible, an option for JSON saving by default (if it’s still select-able as an asset within Unity, such as it is now), or, an option to save a .json file alongside the .asset file, is still on my wish-list for NodeCanvas

    I know (from what I read), as a user we can’t selected a specific serialization format for specific asset files, is that possible in code for you to easily switch the asset files to use YAML? Or does it -have- to be Unity’s global setting?

    The reason I ask is because while converting my entire project to YAML works alright (aside from unsigned integer errors from Unity 5+), importing third party assets can break (from what I read, and…)

    I verified this twice, because the very next package I imported wasn’t working properly, even though no errors are thrown, and I only knew it was an import problem because I had just read about the issue and reverted to a previous git commit to test,

    The workaround, I read from the internet, is to switch your project to ‘Mixed Serialization’, import the third party asset, then switch BACK to “Forced Text Serialization”, which all-in-all, is time consuming and a huge pain to be honest.

    My real push for having NodeCanvas things saved in a somewhat text readable format for A) git, B) comparing and retaining information, is because NodeCanvas is in effect replacing what we would be writing in code, and your JSON export is really readable. Let me know what you think!

    Plus, comparison of NodeCanvas JSON vs Unity’s YAML:

    NodeCanvas:

    vs Unity…

    (Which you can paste into a JSON beautifier, but it’s still far, far less readable than NodeCanvas’ export I think)