Rename related field new to build 254?

After installing build 254 and using refactor/rename to rename a private instance field which has an associated public getter the refactor dialog has an extra step for "rename related field". At least so far I've always unchecked as the fields are related but not the same so renaming them to be the same of course causes compiler errors.

Is this behavior new to 254 or something I just never noticed before? In any case, I think the selection of whether rename related fields is checked/unchecked should be saved so I don't have to keep unchecking it. Heck, I'd love an option to just turn this feature off as I can't imagine I'd ever use it (not enough preview so I wouldn't trust it--the one time I used it it created a ton of compiler errors).



Please sign in to leave a comment.