Source Editor Vue component updates

Update the vue component to be used as the single entry point for Vue applications. At the moment, we do not enforce usage of the Vue component because of the limitations it has (lack of extensions support, lack of event listeners support, etc.). This issue is about making the component respect all the core features of Source Editor to the point where every instance of the editor within a Vue application could be replaced with the Vue component and set up using props instead of getting to the core editor object of the component.

Testing

Please include a SET in MR reviews

changed milestone to %14.9

added Development Department Source Editor devopscreate groupeditor [DEPRECATED] labels

added to epic &4861

@ericschurter, @oregand in the light of our source-to-content switch discussion, I prioritize this one for %14.9. Feel free to re-arrange as you see fit

That sounds like a good plan, thanks @dmishunov

This looks good to me for %14.9

@dmishunov If I understood correctly from the past week of conversations, this issue is important for both any future direction we pursue related to toggling between Source/Content Editor and for using Source Editor in comments and issue descriptions. Is that accurate?

Yes, @ericschurter, I would say so. The general direction for Source Editor atm seems to be via Vue component. This forces refactoring of applications that use the editor which is a positive trend. But to make sure we deliver our best, the Source Editor vue component should be on par with the raw editor's functionality. So yes, this issue is important for all possible implementations.

Perfect, thanks for confirming @dmishunov. This will be a deliverable for 14.9 then!

set weight to 3

added sectiondev label

added [deprecated] Accepting merge requests label

@dmishunov, please can you add a type label to this issue to help with issue discovery in issue reports.

added auto updated label

added featureenhancement label

added typefeature label

changed epic to &7525

mentioned in issue #349635 (closed)

added Deliverable workflowready for development labels

assigned to @dmishunov

This issue made it to workflowready for development without the addition of a frontend or backend tech stack label. Both will be assigned as a result. Bot policy.

added backend frontend labels

removed [deprecated] Accepting merge requests label

mentioned in issue gitlab-org/quality/triage-reports#6494 (closed)

changed the description

added quad-planningcomplete-action label

@dmishunov This issue looks like it may slip this current milestone. Can you leave a or to signify if you are on track to deliver this issue? Please also consider updating the issue's Health Status or Milestone to reflect its current state, and communicate with your Product Manager as appropriate.

Bot policy.

@dmishunov This issue looks like it may slip this current milestone. Can you leave a or to signify if you are on track to deliver this issue? Please also consider updating the issue's Health Status or Milestone to reflect its current state, and communicate with your Product Manager as appropriate.

Bot policy.

changed milestone to %14.10

@dmishunov This issue looks like it may slip this current milestone. Can you leave a or to signify if you are on track to deliver this issue? Please also consider updating the issue's Health Status or Milestone to reflect its current state, and communicate with your Product Manager as appropriate.

Bot policy.

/cc @ericschurter

removed Deliverable label

added Stretch label

@dmishunov This issue looks like it may slip this current milestone. Can you leave a or to signify if you are on track to deliver this issue? Please also consider updating the issue's Health Status or Milestone to reflect its current state, and communicate with your Product Manager as appropriate.

Bot policy.

/cc @ericschurter

changed milestone to %15.0

added missed:14.10 label

@dmishunov This issue looks like it may slip this current milestone. Can you leave a or to signify if you are on track to deliver this issue? Please also consider updating the issue's Health Status or Milestone to reflect its current state, and communicate with your Product Manager as appropriate.

Bot policy.

/cc @ericschurter

@dmishunov This issue looks like it may slip this current milestone. Can you leave a or to signify if you are on track to deliver this issue? Please also consider updating the issue's Health Status or Milestone to reflect its current state, and communicate with your Product Manager as appropriate.

Bot policy.

/cc @ericschurter

changed milestone to %15.1

added missed:15.0 label

@dmishunov This issue looks like it may slip this current milestone. Can you leave a or to signify if you are on track to deliver this issue? Please also consider updating the issue's Health Status or Milestone to reflect its current state, and communicate with your Product Manager as appropriate.

Bot policy.

/cc @ericschurter

@oregand let's make this a %15.2 Deliverable to get it over the line.

changed milestone to %15.2

added Deliverable label

added missed-deliverable label

removed Stretch label

@dmishunov This issue looks like it may slip this current milestone. Can you leave a or to signify if you are on track to deliver this issue? Please also consider updating the issue's Health Status or Milestone to reflect its current state, and communicate with your Product Manager as appropriate.

Bot policy.

/cc @ericschurter

@dmishunov @ericschurter

I am going to push this into %15.3 for us, let me know if y'all disagree!

@oregand Sounds great!

One question – would this be better classified as typemaintenance since there's no user impact?

@ericschurter

Yeah, I think that makes sense!

changed milestone to %15.3

added typemaintenance label and removed typefeature label

created branch 351761-source-editor-vue-component-updates to address this issue

mentioned in merge request !94307 (merged)

@dmishunov This issue looks like it may slip this current milestone. Can you leave a or to signify if you are on track to deliver this issue? Please also consider updating the issue's Health Status or Milestone to reflect its current state, and communicate with your Product Manager as appropriate.

Bot policy.

/cc @ericschurter

added workflowin review label and removed workflowready for development label

closed

removed workflowin review label