Content: How to draw rectangles and circles on a Canvas and save and restore canvas states.
more >>Content: How to draw rectangles and circles on a Canvas and save and restore canvas states.
more >>Content: Introduction to Canvas, basic drawing APIs, and style settings
more >>Content: How to prevent event bubbling and default events, and precautions for using return false.
more >>Content: Introduction to Different Scenarios for “this”
more >>Content: Using try-catch for Exception Handling in JavaScript
more >>Content: Introduction to Arrays and Array-like Objects
more >>When it comes to making HTTP requests, there are two primary methods: GET and POST. These methods differ in how they handle data transmission and have distinct use cases. Let’s explore these differences in more detail while keeping the initial structure intact:
GET Request: GET requests append data to the URL, making it visible in the address bar. This method is less secure because the data can be easily seen by users. For example:
1 | http://example.com/resource?name=John&age=25 |
POST Request: POST requests place data in the request body, which is not visible in the URL, providing better security.
GET Request: GET requests have limitations on the amount of data that can be transmitted, typically around 4KB. This makes them suitable for smaller data requests.
POST Request: POST requests do not have fixed data size limitations and can be used to send large files and substantial amounts of data.
GET Request: GET requests do not have a request body, resulting in fewer headers and less data transfer. This can lead to better performance.
POST Request: POST requests include data in the request body, which adds headers and increases the amount of data transferred, potentially impacting performance.
Content-Type: application/x-www-form-urlencoded
, which informs the server about the data format being used. This header is commonly used for encoding Chinese characters during transmission.Let’s illustrate these differences with code examples:
1 | // JavaScript code to make a GET request |
1 | // JavaScript code to make a POST request |
In conclusion, the choice between GET and POST requests depends on specific requirements. GET requests are suitable for smaller, less sensitive data, while POST requests are preferred for larger, more secure data transmission, including file uploads.
Contents: Introduction to XML, Parsing and Usage of JSON, Differences Between XML and JSON
more >>#Common Git Commands
Downloading Code
git clone
.Creating a New Project
git init
, develop in this repository, and commit the code after development.Working Directory
The content extracted independently from a particular version of the project. These files are extracted from the compressed database of the Git repository and placed on the disk for you to use or modify.
Staging Area
A file that stores the list of information about files to be committed next. It is usually located in the Git repository directory and is sometimes referred to as the index, but it is generally called the staging area.
Local Repository
The place where Git stores the project’s metadata and object database. This is the most important part of Git. When you clone a repository from another computer, you are copying this data.
Untracked
Files just created in the working directory.
Staged
Files that have been moved from the working directory to the staging area.
Committed
Files that have been committed from the staging area to the local repository.
Modified
Files that have been modified in the staging area.
Initialize a Repository
1 | git init |
Configure User Information
1 | git config --global user.name "Name" |
Check File Status
1 | git status |
Add Untracked Files to the Staging Area
1 | git add file (Separate multiple files with spaces) |
Remove Files from the Staging Area
1 | git rm --cached file (Separate multiple files with spaces) |
Commit the Staging Area to the Local Repository
1 | git commit -m 'Description' |
View Local Repository Commit Records
1 | git log |
Discard Changes in the Staging Area
1 | git checkout -- files |
Discard all changes in the staging area
1 | git checkout . |
Overwrite the Working Directory and Staging Area with a Snapshot from the Local Repository, Discarding Commits After a Specific Commit ID
1 | git reset --hard <commitID> |
Overwrite the Staging Area with the Latest Version from the Local Repository Without Overwriting the Working Directory
Essentially cancels the git add
operation
1 | git reset HEAD |
Create a Branch
If no branch name is provided, it lists the current branches. *
indicates the current branch.
1 | git branch branch_name |
View Remote Branches
1 | git branch -r |
View Local and Remote Branches
1 | git branch -a |
Delete a Branch
1 | git branch -d branch_name |
Switch Branches
1 | git checkout branch_name |
Merge Branches
1 | git merge branch_name (Source branch) |
Create and Switch to a Branch
Equivalent to running git branch
and git checkout
simultaneously
1 | git checkout -b branch_name |
Fetch from Remote Repository Without Merging
1 | git fetch |
Merge Fetched Code
1 | git merge |
Delete Remote Branch
1 | git push origin --delete branch_name |
Create a folder ending with .git
locally, then run the following command in this .git
folder:
1 | git init --bare |
Push Code to a Remote Repository
1 | git push remote_repo_url local_branch:remote_branch |
If the local and remote branch names are the same, you can omit the remote branch name.
1 | git push remote_repo_url local_branch |
Pull Code from a Remote Repository
1 | git pull remote_repo_url remote_branch:local_branch |
If the local and remote branch names are the same, you can omit the local branch name.
1 | git pull remote_repo_url remote_branch |
Clone a Remote Repository
When cloning, an alias origin
is automatically generated for the remote repository.
1 | git clone remote_repo_url directory_name (Optional, defaults to the remote repository name) |
Add an Alias for a Remote Repository
1 | git remote add alias_name remote_repo_url |
View Remote Repository Aliases
1 | git remote |
View the Specific URL of a Remote Repository Alias
1 | git remote show origin |
Push Code Using an Alias
1 | git push origin master:master |
Push Code Using an Alias
1 | git push |
Pull Code Using an Alias
git pull
is equivalent to running git fetch
and git merge
simultaneously.
1 | git pull |
Set Upstream Branch for Tracking After Pulling Code
1 | git branch --set-upstream-to=origin/master master |
origin/master
indicates the remote branch.master
indicates the local branch.Save Work Scene to Temporarily Switch to Other Work
1 | git stash |
Resume Work Scene After Other Work is Done
1 | git stash pop |
Difference Between git pull
and git clone
git clone
automatically creates an alias origin
for the remote repository URL.git clone
automatically tracks remote branches, so you can directly use git pull
to update code..gitignore
Create a .gitignore
file in the project’s root directory to list files that should not be committed, such as project configuration files and node_modules
.
When content is modified and you are unsure what has changed, you can use git diff
to compare differences.
Compare differences between the working directory and the staging area.
1 | git difftool |
Compare differences with a specific commit.
1 | git difftool "SHA" |
Compare differences between two commits.
1 | git difftool "SHA1" "SHA2" |
Compare differences with a branch.
1 | git difftool branch_name |
Content: Introduction to AJAX requests and responses, XMLHttpRequest, AJAX usage in JavaScript, and AJAX usage in jQuery.
more >>tag:
缺失模块。
1、在博客根目录(注意不是yilia根目录)执行以下命令:
npm i hexo-generator-json-content --save
2、在根目录_config.yml里添加配置:
jsonContent: meta: false pages: false posts: title: true date: true path: true text: true raw: false content: false slug: false updated: false comments: false link: false permalink: false excerpt: false categories: false tags: true