Hey @josephbburg,

Thanks for checking out the node graph framework when you're storing your additional custom information have you tried the node.create_property(name, value) function?

have you tried the node.create_property(name, value) function?

I have! But it isn't really doing the task that I am requesting this change for. Regardless of whether the user is using create_property , they can't easily override the behavior of node serialization when serializing node graphs, and it isn't clear what BaseNode.serialize() is doing, if anything at all. I think the current behavior is unexpected. I just want to have the ability to override the function. Right now, I have to override NodeGraph._serialize() in order to do what my PR does (to change one line of code). It is bad to have duplicated code, especially when I am duplicating it from another module!

the purpose of this PR isn't to enable users to store custom data, so much as it is to give users the ability to control how the data is serialized. In my case, I already have a JSON format that I want to be able to stick to, and I have information that is stored in the class declarations that I want to include in the JSON that would be redundant to make a property out of (since it is already available to the Qt part of my code). I am sending data out of Qt into a different system.

the property system is really good for what I'm using it for but it isn't directly related to the reason I am requesting this change. I can store the info in the property system - but I still won't be able to override the serialization, and I will have to run an extra conversion step to get things into my JSON format.

Thanks for your reply!