Step class renaming breaks job execution about issues HOT 5 OPEN

At the moment, I don't know how to auto-rename a step if its class has been renamed. I need to somehow "find out" the new name of the step, then copy its values over. I am open to suggestions on that.

Least I can do is mark the step has invalid and not cause any errors.

from issues.

I didn't inspected deeply how you store references to the step scripts but I believe Unity's serialization system allows to keep references after class renaming since I can see component renaming does not leads to the missing script error in Unity itself.

Are you using Unity's serialization to track references to the steps?

BTW marking step as invalid already looks totally fine to me, though it still will be very painful to lose all configured settings of all renamed step instances =(

from issues.

Are you using Unity's serialization to track references to the steps?

I am using OdinSerializer for serialization.

BTW marking step as invalid already looks totally fine to me, though it still will be very painful to lose all configured settings of all renamed step instances =(

Thing is, how often do you rename Step class names? If you want to change the display name of the step, you can use a Name attribute in StepDescription instead.

from issues.

I am using OdinSerializer for serialization.

Ah, I'm not sure how they handle such case, never worked with Odin serializer before =\

Thing is, how often do you rename Step class names? If you want to change the display name of the step, you can use a Name attribute in StepDescription instead.

Thank you for this tip, but in my case class rename was needed to keep proper architecture of my custom steps (e.g. I created Step1 with some functionality but later I found that I need similar step with some additional features so I needed to rename Step1 to SimpleStep1 \ BaseStep1 etc.).

Also it's a common practice to rename classes during refactoring phase in order to give them more clear and meaningful names if it was not done initially.

I'm afraid without renamed classes reference tracking you may have more similar bug reports in the future since it's a default behaviour in Unity - to keep reference of renamed classes.

from issues.

I would need to get in touch with Odin Serializer development team to discuss this issue. At the moment, I am not confident that this would be fixed in 1.0.3.

from issues.