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

Move @workduck-io/mex-editor inside Extension #77

Merged

Conversation

mukul-mehta
Copy link
Contributor

@mukul-mehta mukul-mehta commented Jun 6, 2022

  • Move the existing @workduck-io/mex-editor at 0.5.0 inside of the extension
  • Change useElementOnChange for backlinks to work properly. This fixes the issue with backlinks
  • Update TagElement and QuickLinkElement for extension editor
  • UI is still fucked for combobox components, need to fix

@linear
Copy link

linear bot commented Jun 6, 2022

WD-1318 [TASK] Move `@workduck-io/mex-editor` inside the extension

Description

A brief description of the task

Purpose

What is the purpose of this task?

Additional Context

Any additional information that needs to be added

@mukul-mehta mukul-mehta changed the title Move @workduck-io/mex-editor inside Extension [WIP] Move @workduck-io/mex-editor inside Extension Jun 6, 2022
@mukul-mehta mukul-mehta requested a review from sahil-shubham June 6, 2022 10:30
@sahil-shubham sahil-shubham changed the title [WIP] Move @workduck-io/mex-editor inside Extension Move @workduck-io/mex-editor inside Extension Jun 6, 2022
Copy link
Member

@sahil-shubham sahil-shubham left a comment

Choose a reason for hiding this comment

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

Tested, things work. Thanks for the migrating the editor inside both the apps.

:shipit:

@sahil-shubham sahil-shubham marked this pull request as ready for review June 6, 2022 15:08
@sahil-shubham sahil-shubham merged commit a44025e into main Jun 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants