The first week of front-end internship

first day

When I came on the first day, I started running the code around ten o'clock. The company issued a computer, but because my computer environment is relatively complete, I used my computer to run the code first.

There are two projects in total, one PC is similar to the management system, and the other is a WeChat applet.

Problems encountered in the process of pulling code:

My computer git pulls the code and reports an error after switching the user name and password; installing git on the new computer cannot pull the code. For my own computer, since I logged in with my own account before, I need to clear the credentials before updating the account, which should be in the system settings; on the new computer, git cannot pull the code, probably because of a version problem, although the version problem is a bit unclear , but it works normally after using the version of my own computer.

Then there is the second problem of running, the dependency problem, the version of nodejs is too high. So I searched and found that there are many ways to manage the version, n, nvm, or uninstall and re-download. nvm didn't know why the download failed, so it uninstalled and downloaded again.

After the code ran out, I found it was very messy and complicated, so I was very anxious. But I was too tired at night, and I wanted to show up when I went back, feeling that life was hopeless. When logging in, different backends will be switched, which is the first time I have encountered it.

the next day

Both the system and the WeChat applet ran out.

It took a long time to hand over the system to others, and after the logic was cleared up, I felt a lot more enlightened; WeChat applets can be optimized, and small bugs can also be fixed.

But when I was fixing a small bug, I found a big bug, which was a bug in uniapp, which was outrageous: the
insert image description here
team leader was handing over to others, and I waited and waited, and I was off work. Who knows when she will finish talking.

third day

On the third day, the applet was changed. The above time manager was changed from one to two, and the default time range was now and seven days ago.

On the afternoon of the third day, one of the problems that was required to change the system was the search part of the quality control. Before that, element-ui’s own filter function was used, and it was required to be changed to filter by comparing the existing data with the background database data.

Although the handover was done the next day, it was still difficult. The main task is to look at the code. The team leader asked me to imitate, so I really tried to imitate, but simple imitation can't solve the problem, it can only visit the shape. Even initiated two requests, the code is very complicated.

But after changing the first search box, I re-checked it and found that it was a very simple problem.

fourth day

What I did in the morning of the fourth day was to change some styles of the system. The previous data was paginated. The request was to allow me to search for the content of the searched content to be paginated, and the parameters were passed directly to the backend. If I searched, I passed in a parameter. , just use size as the pagination parameter after searching.

In the afternoon, it is still optimizing the applet. I have forgotten the specifics, but it seems that the blog still needs to be remembered frequently, and it will be forgotten after a long time.

fifth day

On the fifth day, the style of the WeChat Mini Program page was changed. The system also puts forward a requirement, that is, it is required not to lose focus after the button is clicked. The function of not losing focus is to play a logo.

This problem element-ui has not been solved, so I searched a lot of blogs. But the blog's realization of this can only be described as strange. Therefore, there is no way to write it natively.

It uses one-way binding in the structure, and a similar method of judging the tag with the ternary operator. But it can't always be responsive.

I wrote a lot about vue2 before. When the ref of vue3 is used, if toref is not used, it seems that value is needed to get its value. It was agreed to be delivered at three o'clock, and it was more than four o'clock.

Later, three entries were added to a form. This is the reuse and modification of the code, so there is nothing to say.

Summarize

In the past few days, I have tasks every day. When I receive the tasks, I am anxious, afraid that I will not do well, and I feel very fulfilled after completing them.

In actual combat, I found that many things have not been seen before, and it can be regarded as seeing the application of the real actual combat application to the framework. I also learned a lot of things that I didn't know before.

Another very important thing is that before the git aspect, only the code was written and submitted, and the branch was not involved. Now I know the general process of developing and using git, mainly the application of branches, the pull of code, and the conflicts in actual combat.

The above is the summary of the first week. It will continue to be updated later, welcome to pay attention~

Guess you like

Origin blog.csdn.net/zxdznyy/article/details/131791702
Recommended