You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 20, 2024. It is now read-only.
I believe that defining a method with the same name in two different places is at best confusing and at worst may lead to undesirable application behavior. When calling ref through the application, it's not clear which ref is being referred to without use of the debugger.
Therefore, these two methods should have different names for the sake of clarity.
The text was updated successfully, but these errors were encountered:
The
ref
method is defined in two modules, both of which are included in the projectApplicationController
.The duplicate definitions are here:
I believe that defining a method with the same name in two different places is at best confusing and at worst may lead to undesirable application behavior. When calling
ref
through the application, it's not clear whichref
is being referred to without use of the debugger.Therefore, these two methods should have different names for the sake of clarity.
The text was updated successfully, but these errors were encountered: