Add error details to Distribution Release responses
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 74/100
Research direction
Start by locating the distribution release response models and the definitions for api.projects.distributions.release.get and api.projects.distributions.release.post. Compare the documented response shape, then verify that both file-based and string-based releases expose the optional error.message field when status is failed, for Crowdin and Crowdin Enterprise variants.
Written by the indexing model from the issue text.
Description
The Distribution Release model returned by Get Distribution Release (GET /projects/{projectId}/distributions/{hash}/release, api.projects.distributions.release.get) and Release Distribution (POST, api.projects.distributions.release.post) now includes an optional error object:
error— object withmessage(string); present only when the releasestatusisfailed
This applies to both file-based and string-based distribution releases, in both Crowdin and Crowdin Enterprise. Client libraries should add the field to the distribution release response models so consumers can surface release failures.
References:
- Release Distribution
- Get Distribution Release
- Crowdin Enterprise: Get Distribution Release
- Dominant language
- Python
- Stars
- 69
- Forks
- 39
- Avg merge
- 20h 58m
- Merged PRs (30d)
- 9
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from crowdin/crowdin-api-client-python
-
v2 release planningPossibly taken @andrii-bodnar claimed this today. Open
crowdin/crowdin-api-client-python#286 · 1 assignee ·
-
API bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
crowdin/crowdin-api-client-python#246 · 2 comments · 1 assignee ·
All issues in crowdin/crowdin-api-client-python
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
letsencrypt/cp-cps#353 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
PedestrianDynamics/pyFDS-Evac#394 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
DOI-USGS/pywatershed#421 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
python-pillow/Pillow#10087 · 1 comment ·
Maintainers usually reply within 1 day