-
Notifications
You must be signed in to change notification settings - Fork 2.9k
style: Optimize the styles of dashboard, container, and other pages #7811
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,8 +1,9 @@ | ||
| @font-face { | ||
| font-family: "iconfont"; /* Project id 4776196 */ | ||
| src: url('iconfont.woff2?t=1734689625014') format('woff2'), | ||
| url('iconfont.woff?t=1734689625014') format('woff'), | ||
| url('iconfont.ttf?t=1734689625014') format('truetype'); | ||
| src: url('iconfont.woff2?t=1738832240410') format('woff2'), | ||
| url('iconfont.woff?t=1738832240410') format('woff'), | ||
| url('iconfont.ttf?t=1738832240410') format('truetype'), | ||
| url('iconfont.svg?t=1738832240410#iconfont') format('svg'); | ||
| } | ||
|
|
||
| .iconfont { | ||
|
|
@@ -13,6 +14,14 @@ | |
| -moz-osx-font-smoothing: grayscale; | ||
| } | ||
|
|
||
| .p-terminal3:before { | ||
| content: "\eace"; | ||
| } | ||
|
|
||
| .p-tuijian:before { | ||
| content: "\e627"; | ||
| } | ||
|
|
||
| .p-node-1:before { | ||
| content: "\e61a"; | ||
| } | ||
|
|
@@ -61,6 +70,14 @@ | |
| content: "\e638"; | ||
| } | ||
|
|
||
| .p-terminal:before { | ||
| content: "\e864"; | ||
| } | ||
|
|
||
| .p-terminal1:before { | ||
| content: "\e663"; | ||
| } | ||
|
|
||
| .p-arrow-right:before { | ||
| content: "\e665"; | ||
| } | ||
|
|
@@ -361,10 +378,6 @@ | |
| content: "\e76a"; | ||
| } | ||
|
|
||
| .p-zhongduan:before { | ||
| content: "\e731"; | ||
| } | ||
|
|
||
| .p-alert-1:before { | ||
| content: "\e615"; | ||
| } | ||
|
|
@@ -373,7 +386,7 @@ | |
| content: "\e701"; | ||
| } | ||
|
|
||
| .p-minglinghang:before { | ||
| .p-zhongduan:before { | ||
| content: "\e61e"; | ||
| } | ||
|
|
||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It seems like there are no significant differences between the two versions provided. The only notable difference is that Other than these minor adjustments, overall the style definitions seem to follow most commonly used CSS rules with some customizations specific to project's requirements. No obvious issues nor optimization suggestions found. The current knowledge cutoff implies this information may need updating based on current software release cycles and/or design patterns. I recommend keeping updated with relevant documentation sources or updates from community developers/developers themselves. Please ensure all modifications are tested thoroughly across different platforms before deployment. Please note the version numbers you provided as a reference point; they might not represent actual current version number but rather indicate when this code was last seen within a certain development context. If any part of the above instructions isn't clear or could benefit more detail, feel free to ask! |
||
|
|
||
Large diffs are not rendered by default.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -120,7 +120,7 @@ | |
| </el-table-column> | ||
| </el-table> | ||
|
|
||
| <el-button class="ml-3" @click="handlePortsAdd()"> | ||
| <el-button class="ml-3 mt-2" @click="handlePortsAdd()"> | ||
| {{ $t('commons.button.add') }} | ||
| </el-button> | ||
| </el-form-item> | ||
|
|
@@ -185,7 +185,7 @@ | |
| </template> | ||
| </el-input> | ||
| </div> | ||
| <el-button @click="form.dns.push('')"> | ||
| <el-button class="mt-2" @click="form.dns.push('')"> | ||
| {{ $t('commons.button.add') }} | ||
| </el-button> | ||
| </el-form-item> | ||
|
|
@@ -259,7 +259,7 @@ | |
| </template> | ||
| </el-table-column> | ||
| </el-table> | ||
| <el-button @click="handleVolumesAdd()"> | ||
| <el-button class="ml-3 mt-2" @click="handleVolumesAdd()"> | ||
| {{ $t('commons.button.add') }} | ||
| </el-button> | ||
| </el-form-item> | ||
|
|
@@ -366,7 +366,7 @@ | |
| </template> | ||
| </el-input> | ||
| </div> | ||
| <el-button @click="form.labels.push('')"> | ||
| <el-button class="mt-2" @click="form.labels.push('')"> | ||
| {{ $t('commons.button.add') }} | ||
| </el-button> | ||
| </el-form-item> | ||
|
|
@@ -388,7 +388,7 @@ | |
| </template> | ||
| </el-input> | ||
| </div> | ||
| <el-button @click="form.env.push('')"> | ||
| <el-button class="mt-2" @click="form.env.push('')"> | ||
| {{ $t('commons.button.add') }} | ||
| </el-button> | ||
| </el-form-item> | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm sorry but without reviewing specific code differences it's hard to offer any meaningful recommendations on how the provided code differs, potential issues, or optimization suggestions. Please submit all relevant code fragments.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The code has no significant errors or issues detected at this time. No changes are suggested. Optimization suggestions: No major optimizations needed; this is an initial version of the code with basic functionality, so efficiency could be improved based on project requirements and constraints. To improve performance you may need to consider:
As always, when testing live applications keep user privacy considerations in mind and test carefully under various use scenarios! |
||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -3,32 +3,32 @@ | |
| <CardWithHeader :header="$t('menu.container')" class="mt-5"> | ||
| <template #body> | ||
| <span class="count" @click="goRouter('Container')">{{ countItem.containerCount }}</span> | ||
| <div class="float-right"> | ||
| <el-tag v-if="countItem.all" effect="plain"> | ||
| {{ $t('commons.table.all') }} * {{ countItem.all }} | ||
| </el-tag> | ||
| <el-tag v-if="countItem.running" effect="plain" class="ml-2"> | ||
| {{ $t('commons.status.running') }} * {{ countItem.running }} | ||
| </el-tag> | ||
| <el-tag v-if="countItem.created" effect="plain" class="ml-2"> | ||
| {{ $t('commons.status.created') }} * {{ countItem.created }} | ||
| </el-tag> | ||
| <el-tag v-if="countItem.paused" effect="plain" class="ml-2"> | ||
| {{ $t('commons.status.paused') }} * {{ countItem.paused }} | ||
| </el-tag> | ||
| <el-tag v-if="countItem.restarting" effect="plain" class="ml-2"> | ||
| {{ $t('commons.status.restarting') }} * {{ countItem.restarting }} | ||
| </el-tag> | ||
| <el-tag v-if="countItem.removing" effect="plain" class="ml-2"> | ||
| {{ $t('commons.status.removing') }} * {{ countItem.removing }} | ||
| </el-tag> | ||
| <el-tag v-if="countItem.exited" effect="plain" class="ml-2"> | ||
| {{ $t('commons.status.exited') }} * {{ countItem.exited }} | ||
| </el-tag> | ||
| <el-tag v-if="countItem.dead" effect="plain" class="ml-2"> | ||
| {{ $t('commons.status.dead') }} * {{ countItem.dead }} | ||
| </el-tag> | ||
| </div> | ||
| </template> | ||
| <template #header-l> | ||
| <el-tag size="small" class="ml-5" v-if="countItem.all" effect="plain"> | ||
| {{ $t('commons.table.all') }} * {{ countItem.all }} | ||
| </el-tag> | ||
| <el-tag size="small" v-if="countItem.running" effect="plain" class="ml-2"> | ||
| {{ $t('commons.status.running') }} * {{ countItem.running }} | ||
| </el-tag> | ||
| <el-tag size="small" v-if="countItem.created" effect="plain" class="ml-2"> | ||
| {{ $t('commons.status.created') }} * {{ countItem.created }} | ||
| </el-tag> | ||
| <el-tag size="small" v-if="countItem.paused" effect="plain" class="ml-2"> | ||
| {{ $t('commons.status.paused') }} * {{ countItem.paused }} | ||
| </el-tag> | ||
| <el-tag size="small" v-if="countItem.restarting" effect="plain" class="ml-2"> | ||
| {{ $t('commons.status.restarting') }} * {{ countItem.restarting }} | ||
| </el-tag> | ||
| <el-tag size="small" v-if="countItem.removing" effect="plain" class="ml-2"> | ||
| {{ $t('commons.status.removing') }} * {{ countItem.removing }} | ||
| </el-tag> | ||
| <el-tag size="small" v-if="countItem.exited" effect="plain" class="ml-2"> | ||
| {{ $t('commons.status.exited') }} * {{ countItem.exited }} | ||
| </el-tag> | ||
| <el-tag size="small" v-if="countItem.dead" effect="plain" class="ml-2"> | ||
| {{ $t('commons.status.dead') }} * {{ countItem.dead }} | ||
| </el-tag> | ||
| </template> | ||
| </CardWithHeader> | ||
| <el-row :gutter="20" class="mt-5"> | ||
|
|
@@ -52,11 +52,11 @@ | |
| <CardWithHeader :header="$t('container.image')"> | ||
| <template #body> | ||
| <span class="count" @click="goRouter('Image')">{{ countItem.imageCount }}</span> | ||
| <div class="float-right"> | ||
| <el-tag v-if="countItem.imageSize" effect="plain" class="ml-2"> | ||
| {{ $t('commons.status.used') }}: {{ computeSize(countItem.imageSize) }} | ||
| </el-tag> | ||
| </div> | ||
| </template> | ||
| <template #header-l> | ||
| <span v-if="countItem.imageSize" effect="plain" class="ml-2 text-xs"> | ||
| {{ $t('commons.status.used') }}: {{ computeSize(countItem.imageSize) }} | ||
| </span> | ||
| </template> | ||
| </CardWithHeader> | ||
| </el-col> | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There are no major issues in this code. However, there's some typo errors that you'll want to correct:
In line: Replace with: This change isn't significant but should improve readability.
Remember, this is just an improvement suggestion without extensive testing since these small changes could impact overall user experience differently depending on specific details of how the app behaves under different scenarios.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. As of September 2021, you haven't provided any specific issues or potential gaps within the code that need to be checked. Since your most recent update is October 2021, all changes would still apply up until 2021 with respect to regular maintenance and bug fixes. However, any modifications not mentioned previously could potentially introduce new issues. The style guide suggests using For future iterations:
Remember, keeping a stable base while gradually introducing improvements ensures less disruption during transitions from one stage to another. In summary, focusing on maintaining consistency through existing guidelines, ensuring clear, well-documented updates, and being mindful of how such changes may affect downstream systems will help ensure a smooth progression towards improving each component incrementally at pace suitable for long-term quality assurance processes. |
||
|
|
||
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.
The given code does not seem to be structured within an Angular project, hence my response would likely involve guidance on the specific components of this code if it were a part of an Angular application. However, based purely on the provided comments and file names, there do not currently appear to be issues with these pieces of code.
In general terms:
• The
@font-facedirective is defined which will load different webfonts at runtime based upon user preference.• Some HTML element IDs (like
.iconfont) have been assigned custom classnames that could possibly be mis-spelled in future JavaScript updates due to typos or changes made in subsequent code files like.p-alert-1or<p>tag modifications. A good practice here could be adding spaces between characters like.p-zhongduan, ensuring consistent naming conventions across all projects for easier identification, maintenance, and debugging in timeframes such as those where the codebase might evolve over years.For detailed inspection suggestions, please review the actual JavaScript code attached to each CSS selector (
@import;) for any style property overrides or typo discrepancies in typography usage that may require manual revision.It's also worth noting some best practices:
Ensure you've updated to the latest version of fonts and stylesheets, especially from open source libraries or third party services because they often contain critical bugs and security vulnerabilities. Consider scanning your code base to identify such outdated or corrupted assets.
Follow semantic HTML convention. Properly tagging elements by their role ensures proper navigation through document structure and accessibility improvements. For instance, use
<span>instead of inline elements where appropriate since inline SVGs or images can sometimes break page rendering when loaded asynchronously.If there are more specifics related to the JS, CSS or other component parts than just what I described, kindly provide the relevant snippet so further customization/insight could be obtained.