Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
chore: code style fixes by prettier
Signed-off-by: Jonas <[email protected]>
  • Loading branch information
mejo- committed Sep 17, 2025
commit f1d3c95a24f1e684e6ec00443320e8a5560af1e4
2 changes: 1 addition & 1 deletion src/components/Editor.vue
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@
@outline-toggled="outlineToggled">
<MainContainer v-if="contentLoaded">
<!-- Readonly -->
<template v-if="readOnly || (openReadOnlyEnabled && !editMode)">
<template v-if="readOnly || (openReadOnlyEnabled && !editMode)">
<slot name="readonlyBar">
Copy link
Collaborator

Choose a reason for hiding this comment

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

This slot is used by the collectives app to alter the content of the read only bar. I think we need to keep it so that collectives can continue doing that.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

You're right, sorry about that! I readded the slot. However, it's now a direct child of the MainContainer component, which is the same setup as here:

<MainContainer>
<template v-if="showMenuBar">
<MenuBar v-if="!readOnly" :autohide="false" />
<slot v-else name="readonlyBar">
<ReadonlyBar />
</slot>
</template>
<ContentContainer />
</MainContainer>

Do you think that could be an issue? Personally, I feel it’s better to let the ReadonlyBar handle its own CSS styling.

<ReadonlyBar
:is-hidden="hideMenu"
Expand Down