Skip to content
This repository has been archived by the owner on Mar 13, 2023. It is now read-only.

fix: check min/max value in sync comparison #559

Merged
merged 1 commit into from
Jul 11, 2022
Merged

fix: check min/max value in sync comparison #559

merged 1 commit into from
Jul 11, 2022

Conversation

LordOfPolls
Copy link
Member

What type of pull request is this?

  • Non-breaking code change
  • Breaking code change
  • Documentation change/addition
  • Tests change

Description

Resolves #557 by chceking the min and max attributes for options.

Changes

  • Adds min_value and max_value to the attributes that are compared in sync detection

Checklist

  • I've formatted my code with Black
  • I've ensured my code works on Python 3.10.x
  • I've tested my code

@LordOfPolls LordOfPolls added the Bug::Library A bug in the library label Jul 11, 2022
@LordOfPolls LordOfPolls linked an issue Jul 11, 2022 that may be closed by this pull request
3 tasks
@silasary
Copy link
Collaborator

Is the test failing because of rate limits?

@LordOfPolls
Copy link
Member Author

Is the test failing because of rate limits?

No, its a race condition in the test-bot.

Its editing the user, then checking to see if the change was successful. Sometimes it checks the value before discord sends the data.

@silasary
Copy link
Collaborator

Ah, we should definitely make the tests more resilient to that 😛

@LordOfPolls LordOfPolls merged commit c4f7eea into dev Jul 11, 2022
@LordOfPolls LordOfPolls deleted the sync-fix branch July 11, 2022 07:06
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bug::Library A bug in the library
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG] Command Syncing
2 participants