Skip to content
This repository has been archived by the owner on Jan 3, 2022. It is now read-only.

Following Discord updates a lot of refactoring is needed #13

Open
Neztore opened this issue May 6, 2020 · 1 comment
Open

Following Discord updates a lot of refactoring is needed #13

Neztore opened this issue May 6, 2020 · 1 comment
Labels
bug Something isn't working enhancement New feature or request

Comments

@Neztore
Copy link
Member

Neztore commented May 6, 2020

With the recent updates to intents etc. and just some recent debugging I've realised that the local caches actually miss users a lot more often than I thought.
Possible solutions:

  • GetAllUsers
  • Fetch member manually (not possible as far as I can see, Unless I create a second client and set it to rest mode but even then I think that requries OAuth2 to work)
  • Make Polaris ID based

The latter is my current target. Polaris will be made more ID based - i.e. for commands like WHOIS it will validate the user snowflake consists of numbers but not that it exists in caches before checking for a link. This is far more resilient and a few other things may also need updated.

@Neztore Neztore added bug Something isn't working enhancement New feature or request labels May 6, 2020
@Neztore
Copy link
Member Author

Neztore commented May 6, 2020

Turns out rest mode is apparently "safe" for use with Gateway, meaning users can be individually fetched if they do not exist - fixing a signficant issue.
This means the bot token must now be prefixed, which I've already committed locally and will need to put out.
This means we can:

  • Get specific user
  • Get specific member
  • Get all members for a guild
    and more, which should solve a lot of the bugs that have been appearing lately.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant