Skip to content

feat: use new endpoint to get message status #215

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

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

Conversation

aliel
Copy link
Member

@aliel aliel commented Apr 16, 2025

  • less expensive

@aliel aliel requested a review from 1yam April 16, 2025 18:34
Copy link

Summary:
The PR contains a small change to the URL endpoint in the get_message_status method. The original URL was /api/v0/messages/{item_hash}, which has been updated to /api/v0/messages/{item_hash}/status. This change is likely to be a simple typo fix or a minor adjustment to the API endpoint, and does not introduce any significant risks or changes to the existing logic.

Highlight:

-        async with self.http_session.get(f"/api/v0/messages/{item_hash}") as resp:
+        async with self.http_session.get(f"/api/v0/messages/{item_hash}/status") as resp:

This change involves a straightforward substitution of the URL path, which is unlikely to affect the functionality of the codebase in a significant way. The rest of the method remains unchanged, maintaining the existing behavior of the HTTP request.

@github-actions github-actions bot added the BLUE This PR is simple and straightforward. label Apr 16, 2025
@aliel aliel force-pushed the aliel-message-status branch from 74aca22 to b2106e8 Compare April 16, 2025 18:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BLUE This PR is simple and straightforward.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant