Convert classic fields to prototype fields instead of class fields when run against an addon about ember-native-class-codemod HOT 2 OPEN

@elwayman02 to make sure I understand what you are proposing, you want to:

1. Use the "MyClass.prototype.foo" syntax by default when converting a class in an addon
2. Add an option to use the current behavior instead of the default "MyClass.prototype.foo" behavior

Is that correct? And if so, would you be ok with actually flipping the default so that "MyClass.prototype.foo" syntax is opt it? That way the change is not breaking.

from ember-native-class-codemod.

@asakusuma making it opt-in behavior doesn't actually make sense, because the current behavior is unsafe by default. If anything, the unsafe behavior should be the opt-in (hence the suggestion of creating a second codemod that can be run to aggressively maintain the current behavior). I don't think this is a breaking change at all, it's a bugfix.

from ember-native-class-codemod.