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
What feature(s) would you like to see in RepoSense
As is mentioned in #1965, there are currently a TypeScript interface of User in types/types.ts and a JavaScript class of User in utils/User.ts. The difference between them is that the commits attribute in the interface is optional while it is not in the class. However, as the interface and the class are mostly equivalent, it will be reasonable to remove either of them.
Is the feature request related to a problem?
The interchangeable usage of the User Interface and class implies possible inconsistency.
If possible, describe the solution
Remove either the interface or the class. Removing the class seems to give more advantages considering the runtime.
If applicable, describe alternatives you've considered
Removing the interface may also be reasonable as it may allow more flexibility with class methods in a future context.
Additional context
The text was updated successfully, but these errors were encountered:
Remove utils/user.ts, replace with User interface from types.ts
The User class and interface are equivalent in their usage and their
redundancy seems to be a remnant when the code was migrated from JS to
TS.
Let's remove the User class for consistency and to improve runtime
performance.
What feature(s) would you like to see in RepoSense
As is mentioned in #1965, there are currently a TypeScript interface of
User
intypes/types.ts
and a JavaScript class ofUser
inutils/User.ts
.The difference between them is that theHowever, as the interface and the class are mostly equivalent, it will be reasonable to remove either of them.commits
attribute in the interface is optional while it is not in the class.Is the feature request related to a problem?
The interchangeable usage of the
User
Interface and class implies possible inconsistency.If possible, describe the solution
Remove either the interface or the class. Removing the class seems to give more advantages considering the runtime.
If applicable, describe alternatives you've considered
Removing the interface may also be reasonable as it may allow more flexibility with class methods in a future context.
Additional context
The text was updated successfully, but these errors were encountered: