I must have forgotten to update it because it and spring are no longer
getting along. Hopefully its fixed now.
Also changed the indents in the pom files to spaces to match our
guidelines
This should be the way to resolve the API rate limit with calendar
creation. By randomly assigning new guilds one of n amount of accounts,
we spread out the calendar creation load onto many accounts. This should
overall fix the API rate limit of calendar creation per account as well
as allow further expansion.
Change from /embed/calendar/guild-id/cal-number
to /embed/guild-id/calendar/cal-number
This way we can have event specific embeds and such in the future.
Okay, so its almost fully reactive. The API is still blocking as of
current. Everything else is reactive now:
- Command system
- All utility methods
- Event listeners
- Announcement Thread
- Google calendar auth
Added simple reactive wrappers for google calendar blocking calls
I have no idea if any of this works, but it *should* work. Time to test!
Completely rewrote our in-house logger so that its completely async.
Also designed the new logger so that we could pull it out of this
project and incorporated into our general utils library for all of our
other projects
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 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
NovaFox161