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

perf: how to do code split in a sunmao-ui application #379

Open
Yuyz0112 opened this issue Apr 15, 2022 · 2 comments
Open

perf: how to do code split in a sunmao-ui application #379

Yuyz0112 opened this issue Apr 15, 2022 · 2 comments
Assignees
Labels
feature New feature or request

Comments

@Yuyz0112
Copy link
Contributor

What problem does this feature solve?

When we talk about web UI performance, load speed is one of the most important metrics. The basic idea of improving load speed is to do code splits which let the browser lazy load code.

The code split technical is widely used in our daily development, but in sunmao-ui, we do not have the equivalent ability yet.

lazy load component and trait

TBD

split application schema

TBD

What does the proposed API look like?

TBD

@Yuyz0112 Yuyz0112 added the feature New feature or request label Apr 15, 2022
@Yuyz0112 Yuyz0112 self-assigned this Apr 15, 2022
@tanbowensg
Copy link
Collaborator

Module is one of the ways to split code. It can not only wrap components(which makes the leftTree clearer), but also prevent user using global state everywhere.

@tanbowensg
Copy link
Collaborator

In this issue #417, we discussed using application to render module which means we could use multiple nested sunmao instance to render an appliaction. Further more, we can use router component to render multiple pages application.

@tanbowensg tanbowensg added this to the v0.8 milestone Jun 13, 2022
@tanbowensg tanbowensg removed this from the v0.8 milestone Jul 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants