-
Notifications
You must be signed in to change notification settings - Fork 29
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
chore(VSCode): Refactor KaotoEditor structure #1386
chore(VSCode): Refactor KaotoEditor structure #1386
Conversation
{ | ||
path: Links.PipeErrorHandler, | ||
lazy: async () => import('../pages/PipeErrorHandler'), | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@apupier we could add an About
tab here.
@@ -30,19 +31,6 @@ export class KaotoEditorApp implements Editor { | |||
this.editorRef = createRef<EditorApi>(); | |||
} | |||
|
|||
async getElementPosition() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is no longer used.
} | ||
aria-label="Design canvas" | ||
> | ||
<DesignTab /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No more linking components directly, the router will take care of mounting the right component when needed.
<CatalogModalProvider> | ||
<DeleteModalContextProvider>{props.children}</DeleteModalContextProvider> | ||
</CatalogModalProvider> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These providers already come directly from the DesignPage
, so they are no longer needed here.
Currently, the `DesignPage` component is duplicated to serve the multiplying architecture and the webapp. In addition to that, for the multiplying architecture, we're using a React render approach to navigate between different tabs, whereas in the webapp we use a Router. This commit removes the `Tabs` folder and use the `DesignPage` component directly to reduce the duplication. In addition to that, a Router has been introduced to navigate between the tabs, this as a cleanup for the upcoming tasks.
ec2026d
to
478d37c
Compare
Quality Gate passedIssues Measures |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1386 +/- ##
=======================================
Coverage ? 67.01%
Complexity ? 25
=======================================
Files ? 265
Lines ? 7563
Branches ? 1473
=======================================
Hits ? 5068
Misses ? 2492
Partials ? 3 ☔ View full report in Codecov by Sentry. |
Context
Currently, the
DesignPage
component is duplicated to serve the multiplying architecture and the webapp.In addition to that, for the multiplying architecture, we're using a React render approach to navigate between different tabs, whereas in the web app we use a Router.
This commit removes the
Tabs
folder and uses theDesignPage
component directly to reduce the duplication.In addition to that, a Router has been introduced to navigate between the tabs, this is a cleanup for the upcoming tasks.