I query a reference by article ID, and the schema authors is one existing schema, but this query has no relation to this query; I don’t know what it is the schema role is.
However, if I put a non-existent schema, then it won’t get any results. I guess this schema only affects with permission.
Sorry, but I do not understand your question.
I wonder if the first parameter is not in an unclear direction and if the main effect is with the id parameter.
Referencing returns everything that is referencing this content item.
If you have a an author and articles have a reference to the author, you get all articles that have been written by this author with this method.
In general I would not use this API and leverage graphql instead.
Of course, this is an optional method to call the API in some projects.
If A references B and C, and I want to obtain B, not C, this schema can be set to A or B, C, or any existing schema name. This is my question: What role of the schema parameter play?
The schema here is the same schema as {id}, it is basically there for consistency and to follow RESTful URL principles. But it actually provides no real purpose tbh because the ID is unique for the whole app.
If you only want to have B you can use graphql for that.
That’s OK, I just want to confirm it.
1 Like