-
Type:
Bug
-
Status: Resolved
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 9.10
-
Release Notes Summary:The WebUI resolves the parent field of hierarchical directory entries.
-
Browser:
-
Sprint:nxGang Sprint 10.2.2, nxGang Sprint 10.2.3
-
Story Points:0
The Web UI does not resolve the parent field of hierarchical directory entries, we should add NXfetch.directoryEntry": "parent", "depth": "max" in the http header when retrieving the document.
m3 fox@fox-laptop:~/workspace/nuxeo-web-ui$ git diff
diff --git i/elements/nuxeo-app.html w/elements/nuxeo-app.html
index 9ae70200..5b51a613 100644
--- i/elements/nuxeo-app.html
+++ w/elements/nuxeo-app.html
@@ -255,7 +255,7 @@ limitations under the License.
<nuxeo-document id="doc" doc-id="[[docId]]" doc-path="[[docPath]]"
response="{{currentDocument}}"
enrichers="firstAccessibleAncestor, permissions, breadcrumb, preview, favorites, subscribedNotifications, thumbnail, renditions, pendingTasks, runnableWorkflows, runningWorkflows, collection
- headers='{"X-NXfetch.document": "lock,properties", "X-NXtranslate.directoryEntry": "label", "X-NXfetch.task": "actors"}'>
+ headers='{"X-NXfetch.document": "lock,properties", "X-NXfetch.directoryEntry": "parent", "depth": "max", "X-NXtranslate.directoryEntry": "label", "X-NXfetch.task": "actors"}'>
</nuxeo-document>
<nuxeo-operation id="userWorkspace" op="User.GetUserWorkspace"></nuxeo-operation>
However, the "depth": "max" will not only apply to the directory entry's parent resolution but to all references such as users, groups, documents and this will badly impact default performances.
While marsahlling a directory entry and fetching a field we should simply use the default max value to make sure we fetch all the ancestors (parents
- is related to
-
-
- Resolved
-
- is required by
-
-
- Resolved
-
