Skip to content
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

SWC-7185 #5590

Merged
merged 2 commits into from
Nov 27, 2024
Merged

SWC-7185 #5590

merged 2 commits into from
Nov 27, 2024

Conversation

jay-hodgson
Copy link
Member

No description provided.

@jay-hodgson
Copy link
Member Author

demo.integrated.SRC.file.browser.mov

@jay-hodgson jay-hodgson requested a review from nickgros November 26, 2024 18:55
Copy link
Contributor

@nickgros nickgros left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking forward to trying this!

@@ -23,6 +26,8 @@ public interface FilesBrowserViewImplUiBinder

private EntityTreeBrowser entityTreeBrowser;
private Widget widget;
SynapseReactClientFullContextPropsProvider propsProvider;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consistency nit

Suggested change
SynapseReactClientFullContextPropsProvider propsProvider;
private SynapseReactClientFullContextPropsProvider propsProvider;

// TODO: Should not need to remount, but currently the parentContainer is not shown if the existing react component is updated
// TODO: Bug: The tree is not always auto-expanding (to the path to the parent container Id)
reactFileBrowserContainer.clear();
ReactComponent componentContainer = new ReactComponent();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You shouldn't need to create a new ReactComponent instance, you should just be able to create one instance and call render on it with the new ReactElement. But it's possible you tried that and it resulted in another bug.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, tried. Noted a couple of bugs in TODO comments that would need to be addressed if we're moving forward with this solution

@jay-hodgson jay-hodgson merged commit 125a0e3 into Sage-Bionetworks:develop Nov 27, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants