- 
                Notifications
    You must be signed in to change notification settings 
- Fork 108
Use file.path to track EditorWrapper instances more accurately #2145
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
Conversation
9c9278c    to
    1a5c791      
    Compare
  
    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.
👍 Nice catch
1a5c791    to
    e9ec411      
    Compare
  
    | Rebased and recompiled | 
| /compile amend | 
e9ec411    to
    9af74d1      
    Compare
  
    | /rebase | 
This fixes rich workspace loading when moving a Readme.md into a folder and navigating into that folder. The file.id stay the same, so no new components are created and RichWorkspace stays in an ready=false state because EditorWrapper never emit a new ready event. Signed-off-by: Louis Chemineau <louis@chmn.me> Signed-off-by: Julien Veyssier <eneiluj@posteo.net> Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
9af74d1    to
    a74c263      
    Compare
  
    | Sorry rebased, compiled and force-pushed another time. | 
| /backport to stable23 | 
| /backport to stable22 | 
| /backport to stable21 | 
| The backport to stable22 failed. Please do this backport manually. | 
| The backport to stable21 failed. Please do this backport manually. | 
This fixes rich workspace loading when moving a
Readme.mdinto a folder and navigating into that folder.The
file.idstays the same, so no new components are created and RichWorkspace stays in aready=falsestate because EditorWrapper never emits a new ready event.