Unnecessary more in hierarchy field in funders in ES REST API
Background
In production, if children are listed for a node in hierarchy
in a funder, more
is not included. For example, funder 100008577 has the following hierarchy:
"hierarchy": {
"100006462": {
"100008262": {},
"100005590": {},
"100008261": {},
"100008577": {
"100012432": {}
},
"100009621": {},
"100004870": {},
"100006926": {},
"100006499": {},
"100006943": {}
}
}
In staging the same funder has an unnecessary more
in hierarchy
:
"hierarchy": {
"100006462": {
"100008577": {
"more": true,
"100012432": {}
},
"100009621": {},
"100008261": {},
"100006943": {},
"100005590": {},
"100004870": {},
"100008262": {},
"100006926": {},
"100006499": {}
}
}
Definition of ready
-
Product owner: @ppolischuk1 -
Tech lead: @dtkaczyk -
Service:: label applied -
Definition of done updated -
Weight applied
Definition of done
-
Unit tests identified, implemented, and passing -
Code reviewed -
Available via a staging URL -
Knowledge base reviewed and updated -
Public documentation reviewed and updated -
Consider any impacts to current or future architecture/infrastructure, and update specifications and documentation as needed -
Acceptance criteria met -
extraneous more
in funder hierarchy is not returned in JSON response, matching production behavior
-
Notes
Edited by Patrick Polischuk