A logged in user should be able to see a list of all the decks, see the cards in a given deck (after it is selected from the list, for instance), and see the question and answer on a given card. The forms for creating a deck and creating cards for a deck should be done by now. You should be working on marking a card as answered, correctly or incorrectly, and be able to record that data somewhere. If decks belong to one user and are not shared, then you could record this on your deck, but it’s up to you how you model this.
Where you should be with Code Snippets today
A logged in user should be able to see a list of all public snippets and a list of their own snippets, to create new snippets, and to edit and delete existing snippets. You should have a way to manage copying snippets on the back end at least. You may also be ready to start implementing syntax highlighting with JS by this afternoon or evening.
🔖 Resources
Debugging while you work
Setting a breakpoint can help you figure out what code you need in your views!
By including the ‘X-Requested-With’ header set to ‘XMLHttpRequest’ [in the AJAX request], the view will be able to check if the request is AJAX or not.
# In the view function that handles the AJAX request
request.headers.get('x-requested-with')=='XMLHttpRequest'
Django Views the Right WayThis is a detailed, informative deep dive on function-based views in Django and the reasons why, in the author’s opinion, they are better than class-based views.
jQueryThis is not something I recommend using right now, but I include it here because a lot of the resources about using JavaScript in a web browser refer to it (several of the articles above do). It is not as popular as it once was, and it is incompatible with a framework like React. But you will sometimes come across it, and you may end up working with it at your job, so you might as well recognize it when you see it and look it up if you ever need it.
Checking in on Code Snippets and Flashcards progress
Git collaboration review & questions
Django review & questions
Implementing search
Foreign key recursive relationships
🎯 Project: Code Snippets | Flashcards
Keep on with your end-of-phase project. Today you should have models that you can use in the shell and in your application and at least a solid start on the CRUD functionality your application needs.
You’ve been using Django for about a week now. Can you answer these questions? 🤔
If you want to show one specific book in the browser, how would that work in the urls and the views?
How do forms work in Django? You should be able to talk about form objects and how forms are handled in the views.
Can you create new objects, find objects, and find related objects in the Django shell?
How does Django know if a user is logged in?
How can you implement books with multiple categories?
🎯 Project: Django Team Project
Today we’ll begin our first real team project, with a shared repo. This will require more planning, a lot of communication and coordination, and adding on some new Git skills that will let us collaborate.
You will work in a shared repo and submit one application that your team will build together. You need to discuss who will do what, but keep in mind that the work needs to be shared as equally as possible.
You have two options to choose from for this assignment. Your team should meet to discuss and decide today which one you will do.
Then, the very first thing you should do is determine what models you will need and what attributes and relationships they should have. A diagram can be very helpful here.
This assignment is due next Thursday at the end of the Phase.
Dev Teams
For this project, the first team member listed should accept the assignment and enter the name of your team. The other team members can then accept the assignment and select the repo for their team.
Set up a new Django project from scratch. There is no starter code in the assignment repo.
Make sure to create a .gitignore file to exclude certain files (like your .env file and db.sqlite3) from Git. You can get one specific to a Django project at gitignore.io. Just search for Django and copy and paste the text you find there into your .gitignore file. It should be placed at the root of your repo.
Make sure to create a custom user model, following best practices. Do this before you run any other migrations.This guide may be helpful to you.
You may want to install django-debug-toolbar, django-extenstions, and django-environ, as we have done in previous projects.
Git in VS CodeNot everyone loves using git on the command line like I do. A lot of folks like using the integration in VS Code, so you might want to give it a try. This is a good place to start, but there are many other extensions that you could use as well.
Pair Programming GuideThis template for a pairing session is practical and actionable. There are other resources on this site worth a look as well.
Django docs: Authentication in Web Requests -> django-registation-redux handles some of this for us (giving us the login and logout urls, for instance) but it’s helpful to see other ways you can use the authenticated user.
