View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0025514||mantisbt||api rest||public||2019-02-24 16:33||2019-03-24 21:13|
|Summary||0025514: Subprojects returned in GET project doesn't include `inherit_parent`|
This was raised as part of: https://github.com/mantisbt/mantisbt/pull/1453
This should get its own issue in the tracker and not handled by this PR. From my point of view, Get Project has more issues. Let's say project (1) has three subprojects (2,3,4). For a request GetProject(1) I would expect a response with one project (1) including its subproject list. Actually returned is an array with four projects (1,2,3,4). This is at least not consistent, as for example GetIssue(123) only returns one issue, and not additionally those in relationships.
|Tags||No tags attached.|
@vboctor I would be in favour of a separate GET, which returns a list of the project's (user accessible) subprojects
And as already touched on in PR#1453, don't return those as 'additional' projects (This should have its own issue in
If we agree along this lines, I would look to provide a PR.
@obmsch Let's use this issue to implement a GET for subprojects of a project that corresponds the Add/Update/Delete that you implemented earlier.
Please open an issue for the Get Project issue and submit this as a separate PR.
Thanks for your contributions.
@vboctor I'm working on this, but would like to clarify how to proceed before I go ahead.
After working in the hierarchy stuff, i wonder:
Well, the parent inheritance is a property of the relation, not the node.
What do you mean by "decoupled"?
@cproensa I have seen your PR, and once I figure out how to apply that, I will take a look. For now I am happy to get the git basics right.
I will try to answer/discuss all points in the PR. Just for your question:
In the example, the list of subprojects of p1 contains the grandchild p3. My point was, that simply only adding 'inherit_parent` without adding a reference