Skip to content

Commit 8fbb98c

Browse files
authored
Merge pull request #2390 from pablo-maff/updade-part5b
Update part5b
2 parents e5d353e + 5253e9f commit 8fbb98c

File tree

2 files changed

+46
-41
lines changed

2 files changed

+46
-41
lines changed

src/content/5/en/part5b.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -582,7 +582,7 @@ const Blog = ({ blog }) => {
582582

583583
Implement the functionality for the like button. Likes are increased by making an HTTP _PUT_ request to the unique address of the blog post in the backend.
584584

585-
Since the backend operation replaces the entire blog post, you will have to send all of its fields in the request body. If you wanted to add a like to the following blog post:
585+
Since the backend operation replaces the entire blog post, you will have to send all of its fields in the request body. If you wanted to add a like to the following blog post:
586586

587587
```js
588588
{
@@ -831,7 +831,7 @@ export default Togglable
831831
832832
You can find the code for our current application in its entirety in the <i>part5-7</i> branch of [this GitHub repository](https://github.com/fullstack-hy2020/part2-notes/tree/part5-7).
833833
834-
Note that create-react-app has also a [default ESLint-configuration](https://www.npmjs.com/package/eslint-config-react-app), that we have now overridden. [The documentation](https://create-react-app.dev/docs/setting-up-your-editor/#extending-or-replacing-the-default-eslint-config) mentions that it is ok to replace the default but does not encourage to that:
834+
Note that create-react-app has also a [default ESLint-configuration](https://www.npmjs.com/package/eslint-config-react-app), that we have now overridden. [The documentation](https://create-react-app.dev/docs/setting-up-your-editor/#extending-or-replacing-the-default-eslint-config) mentions that it is ok to replace the default but does not encourage us to do so:
835835
<i>We highly recommend extending the base config, as removing it could introduce hard-to-find issues</i>.
836836
837837
</div>

0 commit comments

Comments
 (0)