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

GUI - Frontend Decoupling #613

Merged
merged 12 commits into from
Jan 16, 2024
Merged

Conversation

dinhlongviolin1
Copy link
Member

@dinhlongviolin1 dinhlongviolin1 commented Dec 15, 2023

Resolves #446 .
Resolves #656.

@dinhlongviolin1 dinhlongviolin1 added 🖰 GUI Related to GUI 🟧 Priority: High Must be addressed as soon ✨New feature 📝Release Notes Impacts the Release Notes or the Documentation in general Gui: Back-End labels Dec 15, 2023
@dinhlongviolin1 dinhlongviolin1 self-assigned this Dec 15, 2023
@dinhlongviolin1 dinhlongviolin1 marked this pull request as ready for review December 15, 2023 06:20
@dinhlongviolin1 dinhlongviolin1 changed the title GUI | Frontend Decoupling (#446) GUI - Frontend Decoupling (#446) Dec 15, 2023
Copy link
Contributor

github-actions bot commented Dec 15, 2023

Coverage report for frontend/taipy-gui

Branches coverage not met for global: expected >=80%, but got 62.22515391380826%

St.
Category Percentage Covered / Total
🟢 Statements
80.62% (+0.09% 🔼)
2296/2848
🟡 Branches
62.23% (-0.58% 🔻)
1415/2274
🟡 Functions
74.72% (-0.28% 🔻)
399/534
🟢 Lines
80.99% (+0.1% 🔼)
2130/2630
Show new covered files 🐣
St.
File Statements Branches Functions Lines
🔴 context/wsUtils.ts 50% 0% 0% 42.86%
🟢 context/utils.ts 100% 70% 100% 100%
🟢
... / Dialog.tsx
80.43% 60.87% 100% 80.43%
🟡
... / TaipyRendered.tsx
66.67% 17.65% 50% 66.67%
🟡
... / index.ts
73.33% 26.67% 50% 72.73%
🟢
... / Expandable.tsx
100% 85% 100% 100%
🟢
... / PageContent.tsx
75% 100% 0% 100%
🟢
... / Pane.tsx
95.12% 73.81% 100% 94.87%
🟢
... / Part.tsx
88% 64.29% 75% 91.3%
🟡
... / Unregistered.tsx
62.5% 0% 0% 60%
Show files with reduced coverage 🔻
St.
File Statements Branches Functions Lines
🟡
... / taipyReducers.ts
64.87% (+0.05% 🔼)
58.47% (+1.18% 🔼)
42.86% (-1.37% 🔻)
64.38% (+0.33% 🔼)

Test suite run success

334 tests passing in 36 suites.

Report generated by 🧪jest coverage report action from 726b46d

FredLL-Avaiga
FredLL-Avaiga previously approved these changes Dec 15, 2023
Copy link
Member

@FredLL-Avaiga FredLL-Avaiga left a comment

Choose a reason for hiding this comment

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

😍

@@ -38,6 +38,9 @@ const Navigate = ({ to, params, tab, force }: NavigateProps) => {
navigate(0);
} else {
navigate({ pathname: to, search: `?${searchParams.toString()}` });
Copy link
Member

Choose a reason for hiding this comment

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

do we want 2 navigate calls ?

Copy link
Member Author

Choose a reason for hiding this comment

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

without the empty navigate call, the app would not do a hard reload. Please let me know if you have any other approach

taipy/gui/external/_custom_page.py Outdated Show resolved Hide resolved
taipy/gui/external/_custom_page.py Outdated Show resolved Hide resolved

def __handle_ws_get_variables(self):
# Get Variables
self.__pre_render_pages()
Copy link
Member

Choose a reason for hiding this comment

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

is this not too costly ?

Copy link
Member Author

Choose a reason for hiding this comment

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

It is necessary though to ensure that we have access to all variables. We can optimize the performance of the method

@FredLL-Avaiga FredLL-Avaiga self-requested a review January 11, 2024 11:02
Copy link
Member

@FabienLelaquais FabienLelaquais left a comment

Choose a reason for hiding this comment

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

👍

FredLL-Avaiga
FredLL-Avaiga previously approved these changes Jan 15, 2024
@FredLL-Avaiga FredLL-Avaiga self-requested a review January 16, 2024 10:26
@dinhlongviolin1 dinhlongviolin1 merged commit e0ba951 into develop Jan 16, 2024
21 of 23 checks passed
@dinhlongviolin1 dinhlongviolin1 deleted the feature/frontend-decouple branch January 16, 2024 10:28
@FabienLelaquais FabienLelaquais changed the title GUI - Frontend Decoupling (#446) GUI - Frontend Decoupling Jan 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Gui: Back-End 🖰 GUI Related to GUI ✨New feature 🟧 Priority: High Must be addressed as soon 📝Release Notes Impacts the Release Notes or the Documentation in general
Projects
None yet
Development

Successfully merging this pull request may close these issues.

API for custom front-end implementation SPIKE-Decouple the front-end from the Taipy GUI backend
3 participants