-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
8 changed files
with
843 additions
and
5 deletions.
There are no files selected for viewing
Large diffs are not rendered by default.
Oops, something went wrong.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
fdsafjni | ||
fdalmsfkldjakfdafd | ||
fdksafmnkjfnjk |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -170,7 +170,187 @@ | |
</div> | ||
</div> | ||
|
||
<div id="project_details"></div> | ||
<div id="project_details"> | ||
<div id="project_details_header"> | ||
<p>❌</p> | ||
<p>_title_</p> | ||
</div> | ||
|
||
<div> | ||
<div id="project_details_directory"> | ||
<div class="dir_level_0"> | ||
<p id="details_Intro" class="details_Dir_option">Introduction</p> | ||
<p id="details_Git" class="details_Dir_option">Git</p> | ||
<p id="details_Features" class="details_Dir_option">Features</p> | ||
<p id="details_Guide" class="details_Dir_option">Guide</p> | ||
<p id="details_Documentation" class="details_Dir_option">Documentation</p> | ||
<p id="details_License" class="details_Dir_option">License</p> | ||
<p id="details_Community" class="details_Dir_option">Community</p> | ||
<p id="details_Faqs" class="details_Dir_option">FAQs</p> | ||
<p id="details_Update" class="details_Dir_option">Update Log</p> | ||
<p id="details_Author" class="details_Dir_option">Collaborator</p> | ||
<!-- <div class="dir_level"> | ||
<p class="dir_title">aaa</p> | ||
<p>Overview</p> | ||
<p>Overview</p> | ||
<p>Overview</p> | ||
<p>Overview</p> | ||
<p>Overview</p> | ||
<div class="dir_level"> | ||
<p class="dir_title">bbb</p> | ||
<p>Overview</p> | ||
<p>Overview</p> | ||
<p>Overview</p> | ||
<p>Overview</p> | ||
<p>Overview</p> | ||
</div> | ||
<div class="dir_level"> | ||
<p class="dir_title">ddd</p> | ||
<p>Overview</p> | ||
<p>Overview</p> | ||
<p>Overview</p> | ||
<p>Overview</p> | ||
<p>Overview</p> | ||
</div> | ||
</div> | ||
<div class="dir_level"> | ||
<p class="dir_title">ccc</p> | ||
<p>Overview</p> | ||
<p>Overview</p> | ||
<p>Overview</p> | ||
<p>Overview</p> | ||
<p>Overview</p> | ||
</div> --> | ||
</div> | ||
</div> | ||
<div id="project_details_content"> | ||
<div id="box_Projects_Intro" class="content-block content-display"> | ||
|
||
<div class="content-block-section"> | ||
<p class="content-block-title-1">Introduction</p> | ||
<pre class="content-block-content-1">Especially thanks to the guiding principals, I think it’s fair to say if you are testing your component or app the same way you would instruct a human to test it in production, then you are doing it right. If your component is taking an API call, and formatting it into Markdown, then you should test that it is actually happening correctly. How the component is rendering (and mimicking it in your test) is an example of testing implementation details. Testing what the component renders is not.I know it’s a fine line, but I think you should include your last line. I also think it’d be great if you could find a way to query by something other than test-id.是的,这种顺序基本可行,因为它提供了呈现项目相关信息的逻辑流程。但是,细微的调整可以改善用户导航并提高清晰度。以下是对当前结构的分析和建议的改进:</pre> | ||
</div> | ||
</div> | ||
|
||
<div id="box_Projects_Git" class="content-block"> | ||
|
||
<div> | ||
<p><a href="#"><img src="/File/Icon/ico_github.png" alt=""></a></p> | ||
<div> | ||
<div> | ||
<p>HTTPS</p> | ||
<p>https://github.com/SeeChen/seechen.github.io.git</p> | ||
<p>Copy</p> | ||
</div> | ||
<div> | ||
<p>SSH</p> | ||
<p>[email protected]:SeeChen/seechen.github.io.git</p> | ||
<p>Copy</p> | ||
</div> | ||
</div> | ||
<p><a href="#">Download ZIP File</a></p> | ||
<p><a href="#">View on GitHub</a></p> | ||
</div> | ||
<div> | ||
<p><a href="#"><img src="/File/Icon/ico_github.png" alt=""></a></p> | ||
<div> | ||
<div> | ||
<p>HTTPS</p> | ||
<p>https://github.com/SeeChen/seechen.github.io.git</p> | ||
<p>Copy</p> | ||
</div> | ||
<div> | ||
<p>SSH</p> | ||
<p>[email protected]:SeeChen/seechen.github.io.git</p> | ||
<p>Copy</p> | ||
</div> | ||
</div> | ||
<p><a href="#">Download ZIP File</a></p> | ||
<p><a href="#">View on GitHub</a></p> | ||
</div> | ||
<div> | ||
<p><a href="#"><img src="/File/Icon/ico_github.png" alt=""></a></p> | ||
<div> | ||
<div> | ||
<p>HTTPS</p> | ||
<p>https://github.com/SeeChen/seechen.github.io.git</p> | ||
<p>Copy</p> | ||
</div> | ||
<div> | ||
<p>SSH</p> | ||
<p>[email protected]:SeeChen/seechen.github.io.git</p> | ||
<p>Copy</p> | ||
</div> | ||
</div> | ||
<p><a href="#">Download ZIP File</a></p> | ||
<p><a href="#">View on GitHub</a></p> | ||
</div> | ||
</div> | ||
|
||
<div id="box_Projects_Features" class="content-block"> | ||
<div class="content-block-section"> | ||
<p class="content-block-title-1">Introduction</p> | ||
<pre class="content-block-content-1"> a Especially thanks to the guiding principals, I think it’s fair to say if you are testing your component or app the same way you would instruct a human to test it in production, then you are doing it right. If your component is taking an API call, and formatting it into Markdown, then you should test that it is actually happening correctly. How the component is rendering (and mimicking it in your test) is an example of testing implementation details. Testing what the component renders is not.I know it’s a fine line, but I think you should include your last line. I also think it’d be great if you could find a way to query by something other than test-id.是的,这种顺序基本可行,因为它提供了呈现项目相关信息的逻辑流程。但是,细微的调整可以改善用户导航并提高清晰度。以下是对当前结构的分析和建议的改进:</pre> | ||
</div> | ||
</div> | ||
|
||
<div id="box_Projects_Guide" class="content-block"></div> | ||
<div id="box_Projects_Documentation" class="content-block"></div> | ||
|
||
<div id="box_Projects_License" class="content-block"> | ||
|
||
<div class="content-block-section"> | ||
<p class="content-block-title-1">LICENSE</p> | ||
<p class="content-block-content-1">本项目使用 <a href="#">MIT</a> 开源许可证进行开发</p> | ||
<p class="content-block-content-1">许可证协议详情请查看 <a href="#">www.example.com</a></p> | ||
</div> | ||
<div class="content-block-section"> | ||
<p class="content-block-title-1">中文</p> | ||
<p id="license_translate">本翻译仅供参考,原文请查看<a href="#license_original">这里</a>,或点击<a href="#">这里</a>。</p> | ||
<pre class="content-block-content-1">这是中文的开源许可证</pre> | ||
</div> | ||
<div class="content-block-section"> | ||
<p class="content-block-title-1" id="license_original">Introduction</p> | ||
<pre class="content-block-content-1">GNU GENERAL PUBLIC LICENSEVersion 3, 29 June 2007</pre> | ||
</div> | ||
</div> | ||
|
||
<div id="box_Projects_Community" class="content-block"></div> | ||
<div id="box_Projects_Faqs" class="content-block"></div> | ||
|
||
<div id="box_Projects_Update" class="content-block"> | ||
<div class="content-block-section"> | ||
<p class="content-block-title-1">2000.08.06</p> | ||
<figure> | ||
<figcaption>Fruit</figcaption> | ||
<ol start="0"> | ||
<li>Apple</li> | ||
<li>Pear</li> | ||
<li>Orange</li> | ||
</ol> | ||
</figure> | ||
</div> | ||
</div> | ||
|
||
<div id="box_Projects_Author" class="content-block"> | ||
<div> | ||
<div> | ||
<img src="/File/Image/Home/home-background.avif" alt=""> | ||
<p>SEECHEN LEE</p> | ||
</div> | ||
<div> | ||
<a href="" class="profile_location">Malaysia</a> | ||
<a href="" class="profile_school">Beijing Institute of Technology</a> | ||
<a href="" class="profile_company">-</a> | ||
<a href="#" class="profile_website">https://seechen.github.io</a> | ||
<a href="#" class="profile_github">https://github.com/SeeChen</a> | ||
<a href="#" class="profile_email">[email protected]</a> | ||
</div> | ||
</div> | ||
</div> | ||
</div> | ||
</div> | ||
</div> | ||
</div> | ||
</div> | ||
|
||
|
@@ -180,3 +360,4 @@ | |
</div> | ||
</body> | ||
</html> | ||
|