-
Notifications
You must be signed in to change notification settings - Fork 699
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Select resource sidepanel #11511
Select resource sidepanel #11511
Conversation
Ran into some issues w/ the way the overflow calculation was done as I tried to adjust the heights of the tabs and their containers themselves This ultimately ends up losing some items which were impacting the calculations which will be fixed in a subsequent commit
KDS commit 047379f579ad7067381a9576edc21abd12ad8378 is a req for this change
891a532
to
2043d71
Compare
8819943
to
b14457f
Compare
776ba5c
to
b14457f
Compare
|
||
function fetchTopicResource(topicId) { | ||
const topicNodePromise = ContentNodeResource.fetchModel({ id: topicId }); | ||
const childNodesPromise = ContentNodeResource.fetchCollection({ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As per our conversation - this is where we could use the new fetchTree method instead, to fetch both the topic and its children in one go.
To limit data, can pass the depth: 1
getParam to only get the immediate descendants. The only thing to be aware of here is that the return data here is that the children are paginated by default.
Can see an example of it in use here:
ContentNodeResource.fetchTree({ |
@AllanOXDi I think that we'll do best to make a new PR w/ the work you and I have done separately from this which will be based on the latest develop. I'll close this PR for now but retain the branch so we have it as reference |
Summary
…
References
…
Reviewer guidance
…
Testing checklist
PR process
Reviewer checklist
yarn
andpip
)