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

fix: Apply viewer wrapper as we do it in text #4278

Merged
merged 1 commit into from
Nov 29, 2024
Merged

Conversation

juliusknorr
Copy link
Member

@juliusknorr juliusknorr commented Nov 28, 2024

Follow up to #4259 to address the issues that come with different vue instances (nextcloud-libraries/nextcloud-vue#6280)

This PR introduces a similar pattern as we do it in text where we have a simple Viewer component that just wraps our main Office component. The main goal is to extend our main Office component from our own vue instance to avoid issues further down the compoent tree (e.g. when initializing NcTextField within a component that is rendered by spawnDialog).

Take it with care, it is mostly replicating what worked on text, but seems to work and not log errors in the console anymore.

Ideally viewer would not leak its vue instance in apps that register a handler nextcloud/viewer#2395 (comment)

@juliusknorr
Copy link
Member Author

/backport to stable30

@juliusknorr
Copy link
Member Author

/backport to stable29

@elzody elzody merged commit 806f407 into main Nov 29, 2024
53 checks passed
@elzody elzody deleted the fix/viewer-wrapper branch November 29, 2024 21:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3. to review Ready to be reviewed bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants