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

Introduce the multi-root editor build #11493

Closed
Mgsy opened this issue Mar 21, 2022 · 9 comments · Fixed by #13532
Closed

Introduce the multi-root editor build #11493

Mgsy opened this issue Mar 21, 2022 · 9 comments · Fixed by #13532
Assignees
Labels
squad:collaboration Issue to be handled by the Collaboration team. support:2 An issue reported by a commercially licensed client. type:feature This issue reports a feature request (an idea for a new functionality or a missing option).

Comments

@Mgsy
Copy link
Member

Mgsy commented Mar 21, 2022

📝 Provide a description of the new feature

The multi-root editor is a perfect fit for specific use cases, however, we don't introduce an easy way to integrate it - it requires creating the custom editor, which might be difficult, time-consuming and hard to maintain.

It would be nice to introduce a new type of build for the multi-root editor.


If you'd like to see this feature implemented, add a 👍 reaction to this post.

@Mgsy Mgsy added type:feature This issue reports a feature request (an idea for a new functionality or a missing option). support:2 An issue reported by a commercially licensed client. squad:core Issue to be handled by the Core team. labels Mar 21, 2022
@huzedong2015
Copy link

How long can it be realized

@huzedong2015
Copy link

@Mgsy This function is urgently needed

@Mgsy
Copy link
Member Author

Mgsy commented Apr 19, 2022

Hi @huzedong2015, unfortunately, due to our priorities and commitments, I can't promise any ETA. We will observe this feature request and track how many 👍 it receives. If it will become popular, we might consider adding it to our roadmap.

@huzedong2015
Copy link

I always have requirements, but my own construction is always wrong, so now I can only use the inline mode to solve it in disguise

@csxxbhm
Copy link

csxxbhm commented May 6, 2022

+1

1 similar comment
@AxxxxxxA
Copy link

AxxxxxxA commented May 6, 2022

+1

@ViLi230
Copy link

ViLi230 commented May 6, 2022

+1+1

@scofalik scofalik added squad:collaboration Issue to be handled by the Collaboration team. and removed squad:core Issue to be handled by the Core team. labels Feb 3, 2023
@scofalik scofalik self-assigned this Feb 3, 2023
@CKEditorBot CKEditorBot added the status:planned Set automatically when an issue lands in the "Sprint backlog" column. We will be working on it soon. label Feb 3, 2023
@CKEditorBot CKEditorBot added status:in-progress Set automatically when an issue lands in the "In progress" column. We are working on it. and removed status:planned Set automatically when an issue lands in the "Sprint backlog" column. We will be working on it soon. labels Feb 21, 2023
niegowski added a commit that referenced this issue Mar 1, 2023
Feature (multi-root-editor): Introduced multi-root editor type that allows defining multiple editable areas handled by one editor instance. Closes #11493.

Feature (build-multi-root): Introduced new editor build featuring multi-root editor.

Other (core): `EditorConfig#initialData` and `EditorConfig#placeholder` can now be set to `Record<string, string>` where keys are root names and values are settings for related roots.
@CKEditorBot CKEditorBot removed the status:in-progress Set automatically when an issue lands in the "In progress" column. We are working on it. label Mar 1, 2023
@CKEditorBot CKEditorBot added this to the iteration 61 milestone Mar 1, 2023
@nawein
Copy link

nawein commented May 2, 2023

how to load and save comment data in predefined multi-root code

@scofalik
Copy link
Contributor

scofalik commented May 4, 2023

Do you mean HTML comment feature (<!-- !-->) or do you mean Comments (collaboration) feature?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
squad:collaboration Issue to be handled by the Collaboration team. support:2 An issue reported by a commercially licensed client. type:feature This issue reports a feature request (an idea for a new functionality or a missing option).
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants