Skip to content

branch-3.1: [opt](UI) Optimization for frontend UI #49783 #59718

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.

Sign up for GitHub

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

Jump to bottom
Closed
github-actions wants to merge 1 commit into from
Closed

branch-3.1: [opt](UI) Optimization for frontend UI #49783 #59718

github-actions wants to merge 1 commit into from
+16 −5

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Jan 9, 2026

Cherry-picked from #49783

@zhiqiang-hhhh
[opt](UI) Optimization for frontend UI (#49783)
bce9d52 
### What problem does this PR solve?

1. Change font of profile in web-ui to 'Menlo, Monaco, 'Courier New',
monospace', so that the formatting is more organized.
2. Process whiteSpace in frontend UI, speed up fetching profile.

```text
Changed Session Variables:
VarName       | CurrentValue | DefaultValue
--------------|--------------|-------------
profile_level | 2            | 1           

```
@github-actions github-actions bot requested a review from morrySnow as a code owner January 9, 2026 08:54
@hello-stephen
Copy link
Contributor

hello-stephen commented Jan 9, 2026

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@dataroaring dataroaring closed this Jan 9, 2026
@dataroaring dataroaring reopened this Jan 9, 2026
@hello-stephen
Copy link
Contributor

hello-stephen commented Jan 9, 2026

run buildall

@hello-stephen
Copy link
Contributor

hello-stephen commented Jan 9, 2026

FE UT Coverage Report

Increment line coverage 0.00% (0/4) 🎉
Increment coverage report
Complete coverage report

@morrySnow morrySnow closed this Jan 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@morrySnow morrySnow Awaiting requested review from morrySnow morrySnow is a code owner

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@hello-stephen @dataroaring @morrySnow @zhiqiang-hhhh