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: Add Vulkan Error #11

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

WIP: Add Vulkan Error #11

wants to merge 1 commit into from

Conversation

Xananax
Copy link
Collaborator

@Xananax Xananax commented Mar 22, 2024

Following on https://discord.com/channels/212250894228652034/1210613462288437288

I'm not too sure about the command name, and neither about what the client accepts in terms of formatting (can it do markdown links? Or do we have to use setUrl?), so this is just a first draft.

@winston-yallow
Copy link
Owner

winston-yallow commented May 17, 2024

Hmm, thinking about this more I'm not so sure anymore if it's good adding such a specific command to the bot. I feel like this would be better suited for the docs (also for maintaining the information), and then maybe a command that links there.

(I won't be blocking this if it's wanted, just a thought that I had)

@winston-yallow
Copy link
Owner

I'm not too sure about the command name

I would call it vulkan-troubleshooting. But vulkan-error is fine too, don't think it matters a lot as it's a slash command and has a description showing up in the UI.

what the client accepts in terms of formatting (can it do markdown links? Or do we have to use setUrl?

Everything that a normal message can contain should be fine, so markdown links will work. setUrl would make the whole thing clickable, not only the specific text snippet.

@Xananax
Copy link
Collaborator Author

Xananax commented May 20, 2024

I don't actually know if it's wanted, in my opinion it's not really a great place, but nanachi wanted it. Since we agreed on it on Discord, and it's been a while, I suggest to merge nonetheless, it'd be a bit bothersome to come back a month later and say "actually...".
But also not insisting either way.

@winston-yallow
Copy link
Owner

Alright, then let's merge this. Any objection if I change the command name to something like /troubleshoot vulkan-error? We can then later include other troubleshooting subcommands

@Xananax
Copy link
Collaborator Author

Xananax commented May 30, 2024

That sounds good to me, but I'm currently too overwhelmed to get back on this atm. If you don't do it, I'll get back to it at some point in the next few weeks.

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.

2 participants