WittleWolfie/WW-Blueprint-Core

Consider aliasing renamed methods

Closed this issue · 2 comments

Renaming the methods is convenient for describing the functionality of a method. However, renaming can also obfuscate the original component.

e.g. ActionEnterToDungeon is implemented by TeleportToLastDungeonStageEntrance which is not obvious if you already know you need ActionEnterToDungeon.

As an extension of this: comments should link to all the methods for a given type.

Instead I'm just adopting a policy of keeping names close to the type unless really necessary.