preface

The year 2020 is like a dream, passing by in a flash. Suddenly, we have to make a summary of 2020. We don’t know where to start.

After 2020, I began to reorganize my mood and continue my programming journey. At this time, I began to consciously read the source code of the open source library and began to think about the front-end and the usage scenarios of the code. This led to the constant rhythm of potholes. During the period in order to meet the thirst for knowledge, over vue2 source code, find out the general idea of VUE2 source code. Took a look at common algorithms like sorting and trees. I made a game project with KOA2 and VUE, during which I also experienced CI/CD abilities. I won’t go into details, because most of the process is pretty boring. Behind, must say some interesting content 🙂

Participate in wangEditor

It’s worth going into detail and joining the wangEditor team to do open source work. I have always been interested in open source and found it fascinating. When I first started working, I even went to see github’s official series on how to get involved in open source. However, due to my ability and lack of a good entry point, I did not take further action, but the github library did use a lot of =_=. Until 2020, I took the opportunity to join the WangEditor team, which is the first step to open source. I encountered a lot of problems in the middle, and finally integrated into the small group, of course, in this process is also a lot of benefits.

Git and multiplayer collaboration

Multiplayer collaboration and Git-related issues have been a bit of a weakness in the past. During this period, I went over the knowledge of Git and git workflow again and made some records. The result is this summary of git common scenarios, which will probably be followed by additional git articles. Dig a hole first and fill in later. One caveat about Git is that while there are a lot of very useful graphical Git tools out there, learning and becoming familiar with git commands is a great way to give you a fundamental understanding of what’s going on and feel more in control.

Automated testing

Automatic testing this piece, although written before, but not into a system, into a scale to use, and can not fully appreciate its benefits. In wangEditor, a project with a certain size, I began to write unit tests and even E2E tests seriously. I have to say, this stuff smells good. The use of automated testing for code quality, functional integrity of the improvement is really not the least, it is a strong guarantee to ensure the good operation of the project. If you are interested in learning more about automated testing, you can check out the related resources, as well as the team leader’s article on reliability in good unit testing.

The English translation

With the development of this project, foreign developers began to pay attention to this project, so we have this part of the content to promote. English is a challenge for our domestic developers, but it is also indispensable, after all, a lot of good content in open source is written in English. So I also participated in this part of the content, and spent a lot of time on this part. At the same time, it is also forcing myself to improve my English

Challenges encountered

Rich text editors are known as “tiankeng” on Zhihu, so there are some interesting challenges when it comes to getting into the game. For example, ensure consistent command behavior across browsers, and use the browser’s native capabilities to effectively control cursor position. There is also the need for plug-ins, subcontracting, and editors to move towards L1 levels (browser-based contenteditable capabilities, autonomous implementation of operational commands). By the way, if you’re interested in open source and rich text, try joining our wangEditor open Source team.

Some thoughts after participating in wangEditor 🤔

For this paragraph stay not to think for a long time, think to write all write to keep it. Open source is becoming more and more popular around the world, and I have chosen to join this trend. Everyone has their own reasons for participating in open source. I just like programming and want to do some input and output to improve my ability. People are idealized, leaving this paragraph of text only hope that they can live up to the original intention, can continue to input and output, not three days of fishing two days in the sun net. Of course, it’s best to always do what you love and want to do

About 2021

I also tried to write something for output before, but I always felt that my ability and accumulation were not enough, and what I wrote was relatively shallow, so I abandoned it. I started to get into programming a little bit, and I wanted to take the opportunity to do some input and output.

The scaffold tool that has always been at heart read aloud before also began to get up slowly, interested can kangkang github.com/hahaaha/web… Continue to dig a hole…

If you are writing articles, set up a flag first, and maybe write some git knowledge and functional programming articles later. Those who are interested in these two aspects can pay attention to the first wave 🙂

The last

If you want to do open source in your spare time, please consider joining our team