Features

[koh1project]

What I have done

• Published one article
• Set lint rules
• Identify one type of error
• Modify index export pattern

What I had already known

• OOP approach
• ESLint would fix import order

What I have acquired this week

• The apollo-server-testing library was deprecated and I did not check it, resulting in causing one typing error and using ts-ignore. I should have checked the library information in the official document.
• The experience to publish an article. It took a long time and needed effort, and also realized me what I did not clearly knew the target information.
• Understood why the index export pattern seems like an anti-pattern.

closes #42 #41 #43

[kei95]

@koh1project I'm confused by the commit history and this PR. Would you create a different PR for your changes? I don't think it's a good idea to reopen closed PR and add changes to it. You can even create different branches for each change as it's not realistic to review thousands of lines at once. Make sure not to open a big PR since that would increase the chance to slip errors in. It's pretty important to keep your PR easy to review because of it

[koh1project]

@kei95 I am sincerely sorry for making confusion. I made 2 mistakes, forgot to merge on the browser, and used the same branch name, resulting in this PR page unintentionally containing additional changes including the newest PR's changes. I will make sure such things never happen again.

[kei95]

@kei95 I am sincerely sorry for making confusion. I made 2 mistakes, forgot to merge on the browser, and used the same branch name, resulting in this PR page unintentionally containing additional changes including the newest PR's changes. I will make sure such things never happen again.

No need to apologize!