This commit introduces the r2dbc api for all database handling to make
it fully reactive so future updates to make the bot fully reactive.
While most calls to the database are still blocking, this does use a
reactive driver for it so further work down the line will be able to use
the database reactively without much additional work.
These changes have not been tested, and will need to be tested
thoroughly as database use is the backbone for the bot's persistence
data scheme.
Added the timestamp to the webhooks used for logging so that staff can
know easily when the message was pushed to the webhook, rather than just
when discord received it in the event of several messages within a few
seconds, as discord only shows down to the minute
We have narrowed down where the slowdown starts and ends, however there
is still a lot of things happening between there, so therefore we are
checking what parts of those sections of the code are causing issues.
Its taking, on average, 10-15 seconds to handle this request. To combat
this, we are adding a bunch of debug statements to diagnose *where* the
slowdown is occurring. The next part of this debugging process is to
figure out *why* it is running slow, and how to speed it up to
acceptable speeds.
Messed out how to deploy to repos in the poms as I forgot how to do it,
this issue is now fixed and it will correctly go through the deploy goal
while only actually deploying core to the repos.
This is because they become out of range of JS's `number` type and cause
problems. So, by handling them as strings, and only strings withing the
API, this solves the issue and we should not run into precision issues
anymore.
All packaged files, such as our js, css, and vendor files are removed
from the repository as these should become present at build time, not
during development.
This changes the revision number to be correct, as well as add
distribution management for discal core as this is the main API the bot
uses for object handling and utilities
This commit changes the side bar icons of the modules tab to better show
their respective module, as well as fixes the active highlight on the
selected guild in the guilds tab
This starts work on adding other dashboard modules by defining the page
in data as well as adding in links for the modules and highlighting
active page dynamically (hopefully).
If the user is not logged in, spring will redirect the user to the main
dashboard page, instead of the dashboard guild page where it won't work
due to the API key and user info not being provided
