Conversation
|
Right now I'm sorta like the "Gate Keeper" of the production api. At some time in the future you'll find yourselves as that person(given you were the one who initially setup the project). The other situation might be you're just a professional and the company gave authority to everything to you. Whatever the case may be, know following this process of PRing features, updating PRs to match criteria as well as "fixing PRs" so it can deploy to production is the skill we're exercising. It should be fun practice. After all if we wanna work at Facebook on React they would do the same thing to update the code base. |
|
Also, long story short, we already configured heroku to use yarn so we need to remove If we want want to continue using npm instead of yarn on the cli we can just be careful not to run Or we could add this file to Alas, the challenge with programming sometimes is that there can sometimes be too many ways to solve a problem. haha
The reason it might be good to add to What you guys think? Should we also include |
1 participant
If we look at the app in production right now we'll see that the api fails.
This is because when the project loads all the source files our petition isn't loaded correctly so throws an error. After fixing that we see the destructuring also throws an error so we fix that while we're here.