Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Discuss] Upcoming changes. #35

Open
JABirchall opened this issue Mar 15, 2019 · 2 comments
Open

[Discuss] Upcoming changes. #35

JABirchall opened this issue Mar 15, 2019 · 2 comments

Comments

@JABirchall
Copy link
Owner

Hey everyone, Just a quick update.
Maybe people have been contacting me if this project is abandoned, it wasn't, I was just demotivated. I made some bad architecture decisions when initially building the bot which lead to some problems later in development, and I didn't want to fix them.

I recently started work on NimdaDiscord and learned some new stuff which I want to incorporate into NimdaTS3. These changes will be Breaking Changes.

In the coming months, I am going to slowly and thoughtfully refactor NimdaTS3 with the changes I have wanted to do all this time. Plugins and timers will be correctly abstracted and containerized. Commands will be dynamically parsed into arguments so you won't need to do this in the plugin code.

@element-code
Copy link

@JABirchall im intrested in helping you with the refactoring proccess!

Can you list the structural decisions which you want to change?

@JABirchall
Copy link
Owner Author

Mostly decisions I have made with NimdaDiscord.

Plugin/Event/Timers Containers
Command Parsing
As you pointed out in another issue, removing the vendor from the git repo. (this is a remanent of an old Timeout issue that was pending being merged for months)
Better abstraction of database so plugins, timers and event all have defined access.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants