Manager Loading Logic Enhancement

[Amgelo563]

What

Currently, managers' loading logic is pretty much hard-coded and limited for the developer.

This enhancement suggest making them a little more abstract by adding methods that explicitly load a Command/Event/Schedule class, such as #add(), #remove() or even #edit().

Why

On insight the current way stuff works doesn't give the developer many ways to interact with the manager data. Pretty much the only way to do so is by directly interacting with the cache, which doesn't seem pretty safe and could potentially lead to some problems.

How

Methods like these would need to be added to each manager, each with their own logic:

CommandManager.add(command: AbstractCommandSubclass)
EventManager.add(event: EventSubclass)
ScheduleManager.add(schedule: ScheduleSubclass)

Still need to decide though whether:

• Completely remove all directory logic. This would give index.ts a little more work since all the current folder logic would go there (and ultimately, the developer using the template since the index.ts is supossed to be the one that is always overridden with their own implementation).
• Use a Manager#loadDefaults() called upon manager load where all the directory load logic would be transfered.

---

Ultimately if someone has any opinion, you can let me know on the comments of this issue 👍

[Amgelo563]

This will be addressed on the upcoming nyx framework