✨(frontend) Interlinking doc #904
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add a homepage feature flag that we will propagate to the frontend. It will be used to enable or disable the homepage at runtime.
If the homepage feature flag is enabled, the homepage will be displayed.
The homepage is now accessible at the /home URL. Before the homepage was accessible on the /login URL. We still keep the /login URL for backward compatibility.
This should work in both cases: - search for "vélo" when the document title contains "velo" - search for "velo" when the document title contains "vélo"
Refacto useCunninghamTheme, we don't need a function to have access to the tokens anymore.
We will serve the config from the cache if available in waiting for the config to be loaded. It will remove the loading time for the config except when the config is not available in the cache.
When 2 docs are created almost at the same time,
the second one will fail because the first one.
We get a unicity error on the path key already
used ("impress_document_path_key").
To fix this issue, we will lock the table the
time to create the document, the next query will
wait for the lock to be released.
Info message so people fulfill their licencing obligations Signed-off-by: virgile-deville <[email protected]>
With the soft delete feature, relying on the is_leaf method from the treebeard is not accurate anymore. To determine if a node is a leaf, it checks if the number of numchild is equal to 0. But a node can have soft deleted children, then numchild is equal to 0, but it is not a leaf because if we want to add a child we have to look for the last child to compute a correct path. Otherwise we will have an error saying that the path already exists.
Added several new dependencies to the `package.json` file, including `@dnd-kit/core`, `@dnd-kit/modifiers`, `@fontsource/material-icons`, and `@gouvfr-lasuite/ui-kit`.
Added a new feature for moving documents within the user interface via drag-and-drop. This includes the creation of Draggable and Droppable components, as well as tests to verify document creation and movement behavior. Changes have also been made to document types to include user roles and child management capabilities.
New components were created to manage subpages in the document tree, including the ability to add, reorder, and view subpages. Tests were added to verify the functionality of these features. Additionally, API changes were made to manage the creation and retrieval of document children.
- Created new files for managing subdocuments and detaching documents. - Refactored API request configuration to use an improved configuration type. - Removed unnecessary logs from the ModalConfirmDownloadUnsafe component.
The error modal since next.js 15 are quite intrusive. We decided to hide them.
We want to have a different wording when the child document has no title, so we can distinguish between the two cases.
Move some components and assets to `doc-management` to reduce coupling between features: - SimpleDocItem from `doc-grid` to `doc-management` - useCreateChildDoc from `doc-tree` to `doc-management` - isOwnerOrAdmin from `doc-tree` to `doc-management`
AntoLC
force-pushed
the
feature/interlinking-doc
branch
3 times, most recently
from
1b87c8e to
f949b2d
Compare
AntoLC
force-pushed
the
feature/interlinking-doc
branch
2 times, most recently
from
dc0988e to
d8431c2
Compare
We are now able to create a new page from the slash menu.
We want to be able to interlink documents in the editor. We created a custom inline content that allows users to interlink documents.
We are now able to create a new page from the dropdown search.
We created the editor shortcuts hook to handle the shortcuts for the editor. We implemented the following shortcuts: - "@" to open the interlinking inline content
Create interlinking link mapping for docx and pdf export.
AntoLC
force-pushed
the
feature/interlinking-doc
branch
from
d8431c2 to
87cf9dc
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
Interlinking: ability to mention a doc from another doc (Subpages).
Create connections between subpages directly within the editor.
More here: #679
Proposal
Demo
scrnli_ILshekaeTyer4O.webm