Writing in the front

It’s almost the end of the year, and I believe you are all asking yourself: 2020 is almost over, and this year’s goals for yourself have not been completed.

Remember the goals you set yourself at the beginning of the year:

  • In 2020, you need to at least use the Node API a little bit?
  • If there is no scaffolding, can I build one myself with Webpack?
  • Do you think React should be one of your bread and butter?
  • Does Vue3 also need to be arranged?
  • Does typescript need some work?
  • .

A year passed, also can’t say what also didn’t do, what all did some, but all just dragonfly point a water

It was another year of self-hatred

Joined the wangEditor open Source group for more than a month

As luck would have it, I saw a wangEditor article on the gold nuggets recommendation, and I clicked it to see that the wangEditor open source team was recruiting partners. After an interview with Shuangyue (author of wangEditor) (using Webpack + TS to write a simple rich text), I joined the group.

When writing this demo, I briefly used WebPack + TS and rounded it up to complete some of my small goals for 2020

Join at the beginning, first of all the source code over, from the source code also learned a lot of small skills.

For example, $wrapped in source code (like jquery)

Or take the eventhook idea in the source code

After going through the source code and familiarizing yourself with the team’s development model, start working on issues

One of the problems I’ve noticed while working on user issues in groups is that some developers don’t look at the documentation when using a plugin:

  • Why can’t I download the source code

  • Why upload picture error

  • How to configure the extension menu

In fact, we have a lot of problems above the document how to configure the use of.

But it does happen and there are still unexpected problems after configuration according to the document.

In addition, since it’s an open source project, you need to think more fully about development, such as the requirement I made earlier that all tooltips be destroyed when the editor loses anchor points and is destroyed, both by considering the user’s ability to override the methods exposed by the editor and by considering the structure of the existing code. Speaking of this, the boss was also very patient in code review, guiding which codes were unreasonable and how to design them (unlike our small workshop company, which just implemented functions).

The last thing I like most in the group is the weekly group sharing. There will be a group sharing once a week in the group, and the sharing content is not limited. On the one hand, it can improve the expression ability of the sharing person, on the other hand, it can broaden the knowledge of the audience, which is the best of both worlds.

I hope next time I have the opportunity to share some of the thorny problems I met before.

Write in the last

Post an address for our project:

wangEditor

Welcome to join ~~