ChallengeSentType no longer needed #992
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The Lichess API was updated so that the JSON response to creating a challenge is no longer nested under a single `challenge` heading. All information has been moved to the top level. This commit aligns lichess-bot with the API change. Closes lichess-bot-devs#991.
AttackingOrDefending
approved these changes
Jul 22, 2024
|
Can you add |
It's already there: Line 187 in 067bff6 |
AttackingOrDefending
merged commit 38ab296
into
lichess-bot-devs:master
15 checks passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type of pull request:
Description:
The Lichess API was updated so that the JSON response to creating a challenge is no longer nested under a single
challengeheading. All information has been moved to the top level. This commit aligns lichess-bot with the API change.Related Issues:
Closes #991.
Related Lichess API issue: lichess-org/api#363
Checklist:
Screenshots/logs (if applicable):
N/A