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
While there is no problem with this at all, like classes that are small that doesn't need to be in a new file, this is still refactorable, I think one class per file, moving all classes into their own files makes it look neat, organized, less difficult to find(to potential future readers), and could probably help a bit on debugging as well.
This doesn't have to be done right away.
The text was updated successfully, but these errors were encountered:
I would have preferred to keep SlotKeeper as a private class and not be aware of it from the outside, but I had to make it a public class in order to write tests.
You are right, SlotKeeper is large enough to separate file.
However, it seems odd to have a non-plugin SlotKeeper.ts in the Plugins folder. (Please don't mention VoteCounter.)
I am considering creating a subfolder for each plugins in the plugin folder
Requesting an idea.
There are two (or possibly more) classes in a single file that I saw.
LobbyKeeper
for example, which also has another class inside it calledSlotKeeper
, and possibly more on the other different class files.osu-ahr/src/plugins/LobbyKeeper.ts
Lines 49 to 485 in 24f3b18
osu-ahr/src/plugins/LobbyKeeper.ts
Lines 487 to 604 in 24f3b18
While there is no problem with this at all, like classes that are small that doesn't need to be in a new file, this is still refactorable, I think one class per file, moving all classes into their own files makes it look neat, organized, less difficult to find(to potential future readers), and could probably help a bit on debugging as well.
This doesn't have to be done right away.
The text was updated successfully, but these errors were encountered: