You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Presently the API hides linked components by exposing real repository URL. This was done to make the repo URL usable outside Weblate, but this also complicates editing of the component as the actual setting is not shown.
Describe the solution you would like
Expose real repo (and related) field with the value as is stored in the database. This can break compatibility if somebody relied on the real URL, but will make the API more consistent.
Additionally, add linked_component read-only field so that the actual repo can be easily obtained.
Describe alternatives you have considered
Adding only linked_component field would allow detecting this is a linked component, without breaking existing repo uses. On the other side, there are other fields which are masked this way what makes editing of the linked component via API really tricky.
Screenshots
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the problem
Presently the API hides linked components by exposing real repository URL. This was done to make the repo URL usable outside Weblate, but this also complicates editing of the component as the actual setting is not shown.
Describe the solution you would like
Expose real
repo
(and related) field with the value as is stored in the database. This can break compatibility if somebody relied on the real URL, but will make the API more consistent.Additionally, add linked_component read-only field so that the actual repo can be easily obtained.
Describe alternatives you have considered
Adding only linked_component field would allow detecting this is a linked component, without breaking existing
repo
uses. On the other side, there are other fields which are masked this way what makes editing of the linked component via API really tricky.Screenshots
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: