Replies: 2 comments 1 reply
-
But |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Beta Was this translation helpful? Give feedback.
1 reply
Answer selected by
joubu
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
This is a follow-up for #9556
First, thanks a lot for the "categories" structure. It seems to answer our needs!
However I found several inconsistencies (at least it's how I see things). I am opening this discussion to get feedback on the different points below, I can report them separately with issues if they are confirmed and it's not me misunderstanding how it is supposed to work.
I have the following structure:
project: "koha" > category: "master" > component: "installer"
→ It represents the po file of our installer module for the master branch.
The plan is to have one category per version (23.11, 23.05, etc.) and all our po files under each of them.
weblate://koha/master%252Finstaller
how I would have expected, but onlyweblate://koha/installer
. Which does not make sense for us, as the "installer" components will have to track different branches.GET /api/components/koha/master%252Finstaller/'
returns a link to the category"category": "http://127.0.0.1:8080/api/categories/1/"
. But when I try to reuse it to create a new component using the REST API I get{"category":["Invalid hyperlink - Object does not exist."]}
What am I supposed to use?
GET /api/components/koha/master%252Finstaller/repository/
returns"url": "http://127.0.0.1:8080/api/components/koha/installer/repository/",
, but this url returns a 404.Beta Was this translation helpful? Give feedback.
All reactions