🗓️ Today’s topics

• React Trivia progress
• Organizing your code
• Deploying to Netlify

🎯 Project

The React Trivia application is due on Monday. It should meet at least the minimum functional requirements and is deployed to Netlify. 🚀

Minimum functional requirements:

• A user can see a list of categories.
• A user can select one category.
• A user can see questions for that category, with answer options for each question.
• A user can select an answer for a question.
• A user can see if that answer is the correct answer.

It would be awesome if:

• The answers are shuffled so that the correct answer is not always in the same position.
• The questions are shown one at a time instead of all at once, and the user is able to advance through the set of questions.
• A user can see how many questions they answered correctly (or some kind of score) when they have answered all the questions in a category.

📖 Read | 📺 Watch | 🎧 Listen

• 🎧 Syntax.fm podcast: State in React
• 📖 Component Design in React
• 📺 Jenn Creighton, React Is Fiction

🔖 Resources

• Instructions for deploying a React app to Netlify
• Netlify Docs
• About the Ship It Mindset
• ship it squirrel
• Optional Chaining Operator

👾 Code

• React Devs for Hire Example

🗓️ Today’s Topics

• Views and viewsets
• Nesting and customizing serializers
• Permissions

🎯 Project

Keep on with your API building 😎 💪! What do you need to know to get it working?

By now you should have a list of endpoints that your API offers, even if they are not all complete yet. A good place for this would be in your README, formatted with Markdown. This list should show the URLs along with the HTTP methods/verbs, and ideally should include an example of the JSON that has to be included in the request body (for any requests that send data in the body) and an example of the JSON response that will be returned, for each endpoint. This list will be helpful for your own testing and it can serve as necessary documentation for your API.

Here is an example of what your documentation might look like for an endpoint to create a book:

Create a new book

request

Requires authentication.

title and author are required fields.

POST api/books

{
   "title": "The Anatomy of Melancholy",
   "author": "Robert Burton",
   "publication_year": 1621
}

response

201 Created

{
  "pk": 6,
  "title": "The Anatomy of Melancholy",
  "author": "Robert Burton",
  "publication_year": 1621,
  "featured": false,
  "reviews": []
}

By today or tomorrow, your app should respond with json to GET requests for all habits/books, for one habit/book, and for one book/habit’s associated objects (daily records for habits; reviews or trackers for books). By tomorrow you should also have at least some of your POSTs working, and can begin working on updates and deletes.

💁 Make sure you test your endpoints in Insomnia to confirm that they are working as intended.

Is your app deployed to Heroku yet? 👀 🚀

🔖 Resources

• Django REST Framework Docs
• Article on DRF Generic Views
• Classy DRF

Serializers

• Using Different Read and Write Serializers in DRF
• How to Save Extra Data to a DRF Serializer
• Effectively using DRF Serializers

Permissions

• DRF Permissions
• Built-in Permission Classes in DRF
• Custom Permissions in DRF
• Pro Tip about DRF Permissions This shows how to combine permissions with logical operators like and and or

👾 Code

• Example Recipes API

🗓️ Today’s Topics

• Troubleshooting AJAX requests and getting data on the page
• Using multiple components and conditional rendering to create multiple views of your application

🎯 Project

Continue React Trivia. Remember to take it step by step! Don’t try to do too much at once.

For Thursday, make your trivia categories selectable. When selected, you should show at least 10 questions for that category.

If you can get that working, the next step is to show a single question with answer choices. After that you can make the answer choices selectable.

🔖 Resources

• Using the Effect Hook
• React Conditional Rendering
• 5 Ways to Implement Conditional Rendering in React
• Lifting State Up – This is the official doc page. To see it with hooks, watch the video Lifting State Up with Hooks.
• PropTypes in React - This came up in class today so here’s some more info. Checking types for props is especially useful as your application grows, but it’s ok to leave them out for now while you’re still learning React. (There’s a section at the bottom for how to use them with function components.)

CS resources we talked about in class, relevant to 🌳🌳🌳🌳

• BaseCS Medium post about the tree data structure
• BaseCS Series on Medium
• BaseCS Podcast: Don’t Be Stumped…By Trees
• BaseCS Podcast Main Page

🦉 Code & Notes

• React Devs for Hire App

🗓️ Today’s Topics

Today we dive into Django REST Framework. 🤿

🎯 Project: Choose Your Own Adventure 🐪 🐫

Choose one of the following options.

The application must be deployed to Heroku, whichever option you choose. 🚀

🐪 OPTION ONE: Add an API to Habit Tracker

Add a new app to your existing Habit Tracker project and call it api. Your app should provide CRUD endpoints that return JSON responses.

By Friday afternoon, you should be able to do the following via the API – that is, by making requests using Insomnia.

• list habits
• create a new habit
• view a habit
• update a habit
• delete a habit

By Monday, you should be able to complete all CRUD tasks through the API:

• list habits
• create a new habit
• view a habit
• update a habit
• delete a habit
• list records for a habit (this should be on the habit detail API endpoint)
• create a record for a habit for today (stretch: create a record for any date)
• update a record for a habit
• delete a record from a habit

Write up a list of endpoints you think you will need before you start doing this!

You should develop and test your endpoints using Insomnia. (You can also use the browsable API that DRF gives you in the browser, but you should be comfortable using Insomnia.)

🐫 OPTION TWO: Django Library API

Link to assignment invitation.

Create a new API-only application that lets users keep track of books they are reading, want to read, or have read, and take private or public notes on books.

You should not make forms or templates for this app, but you will need models, urls, views, and serializers. You should use class-based views and return JSON responses.

📖 Read | 📺 Watch | 🎧 Listen

• 📖 REST Resource Naming Guide This resource will be very helpful in thinking about how to structure your urls.
• 🎧 DjangoChat Podcast: DRF
• 📖 DRF class-based views This talks about APIView.
• 📖 Class-based vs. function-based views This is about Django views in general, not specific to DRF.
• 📺 What You Should Know About DRF, Lacey Williams Henschel, PyCascades 2021

🔖 Resources

• Django REST Framework Documentation
  • Installation
  • Serializers
  • ModelSerializer
  • Serializer SlugRelatedField
• 💜 Classy Django REST Framework This is exceptionally useful for working with classes in DRF.
• Python pprint module docs

Blog articles that go with Lacey Williams Henschel’s talk

• What You Should Know About DRF, Part 1: ModelViewSet attributes and methods
• What You Should Know About DRF, Part 2: Customizing built-in methods
• What You Should Know About DRF, Part 3: Adding custom endpoints

🦉 Code

• Recipes App