-
Notifications
You must be signed in to change notification settings - Fork 37
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
SWC-7185 #5590
Conversation
demo.integrated.SRC.file.browser.mov |
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.
Looking forward to trying this!
@@ -23,6 +26,8 @@ public interface FilesBrowserViewImplUiBinder | |||
|
|||
private EntityTreeBrowser entityTreeBrowser; | |||
private Widget widget; | |||
SynapseReactClientFullContextPropsProvider propsProvider; |
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.
Consistency nit
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(); |
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.
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.
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.
Yes, tried. Noted a couple of bugs in TODO comments that would need to be addressed if we're moving forward with this solution
No description provided.