Add dev excuse blog post #714
Conversation
There was a problem hiding this comment.
That was a very nice blog post @maksim36ua! Great job! I particularly liked how each section heading looked like an excuse. :D I left a few comments. Unsure if you'd like another read by anyone or not but it seems almost ready to me.
One thing I definitely would recommend doing is removing the wasp-architecture.png image as it should already be there and called wasp-compilation.png.
| @@ -0,0 +1,268 @@ | |||
| --- | |||
| title: Building a backbone for a full-stack web app with a single config file. | |||
There was a problem hiding this comment.
It seems the other titles do not end in punctuation. Maybe remove the period for consistency?
|  | ||
|
|
||
|
|
||
| ## There’s an issue with the 3-rd party library. |
There was a problem hiding this comment.
I would consider changing 3-rd to third or 3rd.
|
|
||
| Also, we’ve declared a database entity called `Excuse`, queries, and action. The `Excuse` entity consists of the entity’s ID and the text. | ||
|
|
||
| `Queries` are here when we need to fetch/read something, while `actions` are here when we need to change/update data. Both query and action declaration consists of two lines – a reference to the file that contains implementation and a data model to operate on. You can find more info in the docs. So let’s proceed with queries/actions. |
There was a problem hiding this comment.
Maybe we should link to those operations docs when we say "You can find more info in the docs"?
| ```js title=".../ext/queries.js | Defining queries" | ||
| import axios from 'axios'; | ||
|
|
||
| export const getExcuse = async () => { |
There was a problem hiding this comment.
One thing to note, in our internal code we are slowly shifting toward function statements vs arrow expressions, for reasons mentioned here: #487 More of just an FYI for future consistency 👍🏻
Description
Added a blog post for the dev excuse application. This PR includes a post and several images