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

WIP influx packages #257

Closed
wants to merge 17 commits into from
Closed

WIP influx packages #257

wants to merge 17 commits into from

Conversation

swiizyy
Copy link
Contributor

@swiizyy swiizyy commented Jun 12, 2023

Todos

  • Listeners
    • CommandUsage
    • ResourceSync (Usage CPU/MEM, GuildCount)

@swiizyy swiizyy requested review from favna and kyranet as code owners June 12, 2023 10:22
@swiizyy swiizyy marked this pull request as draft June 12, 2023 10:22
@swiizyy swiizyy changed the title WIP influx plugins WIP influx packages Jun 12, 2023
@favna favna force-pushed the feat/influx-utilities/create branch from fc2c576 to 31404a8 Compare June 13, 2023 18:09
Copy link
Member

@favna favna left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah that aint it

favna
favna previously approved these changes Jun 14, 2023
@favna favna dismissed their stale review June 14, 2023 08:14

Woops didn't mean to click approve because there are still merge conflicts

@favna
Copy link
Member

favna commented Jun 17, 2023

Other than that it needs manual testing this looks ready-ish? @kyranet

@favna
Copy link
Member

favna commented Jun 25, 2023

@swiizyy when will you pick up the remaining TODOs?

@swiizyy swiizyy marked this pull request as ready for review July 11, 2023 11:08
@swiizyy swiizyy requested a review from favna July 11, 2023 11:54
}

export function initializeInflux(options: Client.Options = {}) {
if (!process.env.INFLUX_URL) return;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also check whether INFLUX_ENABLED is true (envParseBoolean('INFLUX_ENABLED', true))


protected initTags() {
this.tags.push(
[Tags.Client, envParseString('CLIENT_ID', Buffer.from(envParseString('DISCORD_TOKEN').split('.')[0], 'base64').toString())],
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This always processes the fallback, it's better to do process.env.CLIENT_ID ?? Buffer.from(...).toString().

But at that point, does http-framework not provide a function for getting the client ID? o.o

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, it doesn't seem to me, that's why I reused this... Do you want me to add this option to http-framework?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This entire README needs a rewrite, most of it is shared-http-pieces.

@@ -1,3 +1,3 @@
import { createTsupConfig } from '../../scripts/tsup.config';

export default createTsupConfig({ format: ['esm', 'cjs'] });
export default createTsupConfig({ format: ['esm'] });
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we doing this? cc @favna

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

Successfully merging this pull request may close these issues.

3 participants