Beep boop. Your images are optimized!

Your image file size has been reduced by 12% 🎉

📝 docs | :octocat: repo | 🙋🏾 issues | 🏪 marketplace

~Imgbot - Part of Optimole family

Please describe the changes this PR makes and why it should be merged: a new cache manager class was created as was mentioned in issue #70

Status and versioning classification:

• This PR changes the library's interface (methods or parameters added)
• This PR includes breaking changes (methods removed or renamed, parameters moved or removed)

Which part of the bot is this bug report for?

Database

Issue description

Our current CacheManager class which uses @setar/cache package kinda sucks, so I recommend creating a new class and instead, using the node-ts-cache package which has far more options such as in-memory & file-memory storages.

and not to mention, it has typing decorators and much more to use.

Code sample

import { CacheContainer, ICachingOptions } from "node-ts-cache";
import { MemoryStorage } from "node-ts-cache-storage-memory";

export default class CacheManager <DataObject extends object | unknown> {

    private Container: CacheContainer
    private Storage: MemoryStorage;

    constructor()
    {
        this.Storage = new MemoryStorage()
        this.Container = new CacheContainer(this.Storage);
    }

    //TODO: Add Remove Method
    async remove(key: string, returnObject: false): Promise<undefined | void>
    async remove(key: string, returnObject: true): Promise<DataObject | undefined>
    async remove(key: string, returnObject = true): Promise<DataObject | undefined | void>
    {
        if(returnObject)
        return;

        return;
    }

    async get(key: string): Promise<DataObject>
    {
        return await this.Container.getItem<DataObject>(key);
    }

    async set(key: string, data: DataObject, options?: Partial<ICachingOptions & { check?: false }>): Promise<void>
    async set(key: string, data: DataObject, options?: Partial<ICachingOptions & { check?: true }>): Promise<boolean>
    async set(key: string, data: DataObject, options: Partial<ICachingOptions & { check?: boolean }> = {ttl: 300, isLazy: false, isCachedForever: false, check: true }): Promise<void | boolean>
    {
        const doCheck = ('check' in options) ? options.check : false;
        delete options.check;
        await this.Container.setItem(key, data, options);

        if(doCheck)
            return await this.check(key);
        else
            return;
    }
    
    async check(key: string): Promise<boolean>
    {
        const data = await this.Container.getItem<DataObject>(key);
        if(data)
            return true;
        else
            return false;
    }

    async clear(): ReturnType<CacheContainer["clear"]>
    {
        return await this.Container.clear();
    }
}

Node.js version

16.x.x

Operating system

No response

Priority this issue should have

Medium (should be fixed soon)

Which gateway intents are you subscribing to?

Not applicable (subpackage bug)

I have tested this issue on a development release

No response

Please describe the changes this PR makes and why it should be merged:

• Added Generic types for Mongoose Models and Schemas
• Added Generic Return Types for Database Managers

Status and versioning classification:

• I know how to update typings and have done so, or typings don't need updating
• This PR only includes non-code changes, like changes to documentation, README, etc.

Please describe the changes this PR makes and why it should be merged:

Status and versioning classification:

• Code changes have been tested against the Discord API
• This PR changes the library's interface
• This PR includes breaking changes
• I know how to update typings and have done so

Please describe the changes this PR makes and why it should be merged:

Entering new Music Stage and importing functions and commands by the package of player-engine

Status and versioning classification:

• I know how to update typings and have done so
• This PR changes the library's interface (methods or parameters added)
• This PR includes breaking changes (methods removed or renamed, parameters moved or removed)

Please describe the changes this PR makes and why it should be merged: Endpoints will be tested at each time they are gonna be available on the express server.

Status and versioning classification:

• I know how to update typings and have done so
• This PR changes the library's interface (methods or parameters added)

Please describe the changes this PR makes and why it should be merged: Loading Endpoints by Manager and passing client by Status and versioning classification:

• This PR changes the library's interface (methods or parameters added)

Status and versioning classification:

• I know how to update typings and have done so
• This PR changes the library's interface (methods or parameters added)
• This PR includes breaking changes (methods removed or renamed, parameters moved or removed)

Please describe the changes this PR makes and why it should be merged:

Status and versioning classification:

• This PR changes the library's interface (methods or parameters added)
• I know how to update typings and have done so

Status and versioning classification:

• This PR changes the library's interface (methods or parameters added)
• This PR only includes non-code changes, like changes to documentation, README, etc.