Fix: (2024.02.02) Update API Endpoint Paths, Domain, and Datetime Handling #198
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
- Updated the domain string from ".party" to ".su". - Revised API endpoint paths in the source code from .../api/... to .../api/v1/... to align with changes in the API server's address. - Modified the `format_time_by_type` function for proper handling of ISO 8601 datetime strings, following adjustments to the API server.
|
Yo man. Thanks a bunch for the fix! I think there still some problems though, because when I try to use it with this pull request, it tries to increment the posts by 25, instead of 50, which ends up causing problems with the API EDIT Fixed by going to lines 179 and 181 of |
(Commit message and Description translated by GPT-4) This commit addresses feedback received from Tosh0kan regarding an issue encountered when integrating with a specific pull request. The problem was due to the post increment value being set to 25, which conflicted with the expected value of 50 for proper API functionality. By updating the values on lines 179 and 181 of `main.py` from 25 to 50, this commit resolves the issue and ensures smoother API interactions. **Changes made:** - Updated post increment value from 25 to 50 on lines 179 and 181 of `main.py`. **Acknowledgements:** - Special thanks to Tosh0kan for identifying the issue and suggesting the precise fix needed to enhance our project's compatibility and performance.
Thank you for repair code! |
|
No problem, and sorry I didn't send a proper file |
- Update favourite API url - Fix datetime parsing to fit the timestamp format in creators.json
Adapt API update
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.
2024.02.02
format_time_by_typefunction for proper handling of ISO 8601 datetime strings, following adjustments to the API server.about tmi
It's working perfectly now! (but coomer is so slow to download '-`)
Thank you for your project 🥰