tasks: remove pending tasks in lecture files

jslvtr · jslvtr · commit 8ba2f69fd7c0 · 2022-09-23T11:23:48.000+01:00
diff --git a/docs/docs/05_flask_smorest/02_data_model_improvements/README.md b/docs/docs/05_flask_smorest/02_data_model_improvements/README.md
@@ -5,12 +5,6 @@ description: "Use dictionaries instead of lists for data storage, and store stor
 
 # Data model improvements
 
-- [x] Set metadata above
-- [x] Start writing!
-- [x] Create `start` folder
-- [x] Create `end` folder
-- [ ] Create per-file diff between `end` and `start` (use "Compare Folders")
-
 ## Starting code from section 4
 
 This is the "First REST API" project from Section 4:
diff --git a/docs/docs/05_flask_smorest/03_improvements_on_first_rest_api/README.md b/docs/docs/05_flask_smorest/03_improvements_on_first_rest_api/README.md
@@ -5,12 +5,6 @@ description: "Add new error handling and code improvements to the REST API befor
 
 # Improvements to our first REST API
 
-- [x] Set metadata above
-- [x] Start writing!
-- [x] Create `start` folder
-- [x] Create `end` folder
-- [ ] Create per-file diff between `end` and `start` (use "Compare Folders")
-
 ## Using `flask_smorest.abort` instead of returning errors manually
 
 At the moment in our API we're doing things like these in case of an error:
diff --git a/docs/docs/05_flask_smorest/04_new_endpoints_for_api/README.md b/docs/docs/05_flask_smorest/04_new_endpoints_for_api/README.md
@@ -5,12 +5,6 @@ description: "Let's add a few routes to our first REST API, so it better matches
 
 # New endpoints for our REST API
 
-- [x] Set metadata above
-- [x] Start writing!
-- [x] Create `start` folder
-- [x] Create `end` folder
-- [ ] Create per-file diff between `end` and `start` (use "Compare Folders")
-
 ## New endpoints
 
 We want to add some endpoints for added functionality:
diff --git a/docs/docs/05_flask_smorest/05_reload_api_docker_container/README.md b/docs/docs/05_flask_smorest/05_reload_api_docker_container/README.md
@@ -5,12 +5,6 @@ description: "Learn how to get your code instantly synced up to the Docker conta
 
 # Reloading API code in Docker container
 
-- [x] Set metadata above
-- [x] Start writing!
-- [x] Create `start` folder
-- [x] Create `end` folder
-- [ ] Create per-file diff between `end` and `start` (use "Compare Folders")
-
 ## Updating Dockerfile to use `requirements.txt`
 
 This is the Dockerfile as we've got it:
diff --git a/docs/docs/05_flask_smorest/06_api_with_method_views/README.md b/docs/docs/05_flask_smorest/06_api_with_method_views/README.md
@@ -5,12 +5,6 @@ description: Flask-Smorest MethodViews allow us to simplify API Resources by def
 
 # How to use Flask-Smorest MethodViews and Blueprints
 
-- [x] Set metadata above
-- [x] Start writing!
-- [x] Create `start` folder
-- [x] Create `end` folder
-- [ ] Create per-file diff between `end` and `start` (use "Compare Folders")
-
 Let's improve the structure of our code by splitting items and stores endpoints into their own files.
 
 Let's create a `resources` folder, and inside it create `item.py` and `store.py`.
diff --git a/docs/docs/05_flask_smorest/07_marshmallow_schemas/README.md b/docs/docs/05_flask_smorest/07_marshmallow_schemas/README.md
@@ -5,12 +5,6 @@ description: A marshmallow schema is useful for validation and serialization. Le
 
 # Adding marshmallow schemas
 
-- [x] Set metadata above
-- [x] Start writing!
-- [x] Create `start` folder
-- [x] Create `end` folder
-- [ ] Create per-file diff between `end` and `start` (use "Compare Folders")
-
 Something that we're lacking in our API at the moment is validation. We've done a _tiny_ bit of it with this kind of code:
 
 ```py
diff --git a/docs/docs/05_flask_smorest/08_validation_with_marshmallow/README.md b/docs/docs/05_flask_smorest/08_validation_with_marshmallow/README.md
@@ -5,12 +5,6 @@ description: We can use the marshmallow library to validate request data from ou
 
 # Validation with marshmallow
 
-- [x] Set metadata above
-- [x] Start writing!
-- [x] Create `start` folder
-- [x] Create `end` folder
-- [ ] Create per-file diff between `end` and `start` (use "Compare Folders")
-
 Now that we've got our schemas written, let's use them to validate incoming data to our API.
 
 With Flask-Smorest, this couldn't be easier!
diff --git a/docs/docs/05_flask_smorest/09_decorating_responses/README.md b/docs/docs/05_flask_smorest/09_decorating_responses/README.md
@@ -5,12 +5,6 @@ description: Add response serialization and status code to API endpoints, and ad
 
 # Decorating responses with Flask-Smorest
 
-- [x] Set metadata above
-- [x] Start writing!
-- [x] Create `start` folder
-- [x] Create `end` folder
-- [ ] Create per-file diff between `end` and `start` (use "Compare Folders")
-
 We can use marshmallow schemas for serialization when we respond to a client. To do so, we need to tell Flask-Smorest what Schema to use when responding.
 
 This will do a few things:
diff --git a/docs/docs/06_sql_storage_sqlalchemy/01_project_overview_sqlalchemy/README.md b/docs/docs/06_sql_storage_sqlalchemy/01_project_overview_sqlalchemy/README.md
@@ -5,9 +5,6 @@ description: Let's look at what we'll do in this section. There are no changes t
 
 # Project Overview (and why use SQLAlchemy)
 
-- [x] Set metadata above
-- [x] Start writing!
-
 In this section we'll make absolutely no changes to the API! However, we will completely change the way we store data.
 
 Up until now, we've been storing data in an "in-memory database": a couple of Python dictionaries. When we stop the app, the data is destroyed. This is obviously not great, so we want to move to a proper store that can keep data around between app restarts!
diff --git a/docs/docs/06_sql_storage_sqlalchemy/03_one_to_many_relationships_sqlalchemy/README.md b/docs/docs/06_sql_storage_sqlalchemy/03_one_to_many_relationships_sqlalchemy/README.md
@@ -5,12 +5,6 @@ description: Model relationships let us easily retrieve information about a rela
 
 # One-to-many relationships with SQLAlchemy
 
-- [x] Set metadata above
-- [x] Start writing!
-- [x] Create `start` folder
-- [x] Create `end` folder
-- [ ] Create per-file diff between `end` and `start` (use "Compare Folders")
-
 ```python title="models/item.py"
 from db import db
 
diff --git a/docs/docs/06_sql_storage_sqlalchemy/04_configure_flask_sqlalchemy/README.md b/docs/docs/06_sql_storage_sqlalchemy/04_configure_flask_sqlalchemy/README.md
@@ -5,12 +5,6 @@ description: Link Flask-SQLAlchemy with our Flask app and create the initial tab
 
 # Configure Flask-SQLAlchemy
 
-- [x] Set metadata above
-- [x] Start writing!
-- [x] Create `start` folder
-- [x] Create `end` folder
-- [ ] Create per-file diff between `end` and `start` (use "Compare Folders")
-
 We want to add two imports to `app.py`:
 
 ```python title="app.py"
diff --git a/docs/docs/06_sql_storage_sqlalchemy/05_insert_models_sqlalchemy/README.md b/docs/docs/06_sql_storage_sqlalchemy/05_insert_models_sqlalchemy/README.md
@@ -5,12 +5,6 @@ description: Learn how to use SQLAlchemy to add new rows to our SQL database.
 
 # Insert models in the database with SQLAlchemy
 
-- [x] Set metadata above
-- [x] Start writing!
-- [x] Create `start` folder
-- [x] Create `end` folder
-- [ ] Create per-file diff between `end` and `start` (use "Compare Folders")
-
 Inserting models with SQLAlchemy couldn't be easier! We'll use the `db.session`[^1] variable to `.add()` a model. Let's begin working on our `Item` resource:
 
 ```python title="resources/item.py"
diff --git a/docs/docs/06_sql_storage_sqlalchemy/06_get_models_or_404/README.md b/docs/docs/06_sql_storage_sqlalchemy/06_get_models_or_404/README.md
@@ -5,12 +5,6 @@ description: Learn how to fetch a specific model using its primary key column, a
 
 # Get models by ID from the database using SQLAlchemy
 
-- [x] Set metadata above
-- [x] Start writing!
-- [x] Create `start` folder
-- [x] Create `end` folder
-- [ ] Create per-file diff between `end` and `start` (use "Compare Folders")
-
 Using the model class's `query` attribute, we have access to two very handy methods:
 
 - `ItemModel.query.get(item_id)` gives us an `ItemModel` object from the database where the `item_id` matches the primary key.
diff --git a/docs/docs/06_sql_storage_sqlalchemy/07_updating_models_sqlalchemy/README.md b/docs/docs/06_sql_storage_sqlalchemy/07_updating_models_sqlalchemy/README.md
@@ -5,12 +5,6 @@ description: How to make changes to an existing model, or insert one if it doesn
 
 # Updating models with SQLAlchemy
 
-- [x] Set metadata above
-- [x] Start writing!
-- [x] Create `start` folder
-- [x] Create `end` folder
-- [ ] Create per-file diff between `end` and `start` (use "Compare Folders")
-
 A frequent operation in REST APIs is the "upsert", or "update or insert".
 
 This is an idempotent operation where we send the data we want the API to store. If the data identifier already exists, an update is done. If it doesn't, it is created.
diff --git a/docs/docs/06_sql_storage_sqlalchemy/08_retrieve_list_all_models/README.md b/docs/docs/06_sql_storage_sqlalchemy/08_retrieve_list_all_models/README.md
@@ -5,12 +5,6 @@ description: Get more than one model and return it as a list from the API.
 
 # Retrieve a list of all models
 
-- [x] Set metadata above
-- [x] Start writing!
-- [x] Create `start` folder
-- [x] Create `end` folder
-- [ ] Create per-file diff between `end` and `start` (use "Compare Folders")
-
 Using the `query` attribute of our model class, we can retrieve all the results of the query:
 
 ```python title="resources/item.py"
diff --git a/docs/docs/06_sql_storage_sqlalchemy/09_delete_models_sqlalchemy/README.md b/docs/docs/06_sql_storage_sqlalchemy/09_delete_models_sqlalchemy/README.md
@@ -5,12 +5,6 @@ description: Use SQLAlchemy to handle removal of a specific model.
 
 # Delete models with SQLAlchemy
 
-- [x] Set metadata above
-- [x] Start writing!
-- [x] Create `start` folder
-- [x] Create `end` folder
-- [ ] Create per-file diff between `end` and `start` (use "Compare Folders")
-
 Just as with adding, deleting models is a matter of using `db.session`, and then committing when the deletion is complete:
 
 ```python title="resources/item.py"
diff --git a/docs/docs/07_sqlalchemy_many_to_many/02_one_to_many_review/README.md b/docs/docs/07_sqlalchemy_many_to_many/02_one_to_many_review/README.md
@@ -3,12 +3,6 @@ title: One-to-many relationships review
 description: A super-quick look at creating the Tag model and setting up the one-to-many relationship with Stores.
 ---
 
-- [x] Set metadata above
-- [x] Start writing!
-- [x] Create `start` folder
-- [x] Create `end` folder
-- [ ] Create per-file diff between `end` and `start` (use "Compare Folders")
-
 # One-to-many relationship between Tag and Store
 
 Since we've already learned how to set up one-to-many relationships with SQLAlchemy when we looked at Items and Stores, let's go quickly in this section.
diff --git a/docs/docs/07_sqlalchemy_many_to_many/03_many_to_many_relationships/README.md b/docs/docs/07_sqlalchemy_many_to_many/03_many_to_many_relationships/README.md
@@ -5,12 +5,6 @@ description: Learn to set up a many-to-many relationship between two models usin
 
 # Many-to-many relationships
 
-- [x] Set metadata above
-- [x] Start writing!
-- [x] Create `start` folder
-- [x] Create `end` folder
-- [ ] Create per-file diff between `end` and `start` (use "Compare Folders")
-
 ## The SQLAlchemy models
 
 In one-to-many relationships, one of the models has a foreign key that links it to another model. 
diff --git a/docs/docs/08_flask_jwt_extended/04_flask_jwt_extended_setup/README.md b/docs/docs/08_flask_jwt_extended/04_flask_jwt_extended_setup/README.md
@@ -5,12 +5,6 @@ description: Install and set up the Flask-JWT-Extended extension with our REST A
 
 # Flask-JWT-Extended setup
 
-- [x] Set metadata above
-- [x] Start writing!
-- [x] Create `start` folder
-- [x] Create `end` folder
-- [ ] Create per-file diff between `end` and `start` (use "Compare Folders")
-
 First, let's update our requirements:
 
 ```diff title="requirements.txt"
diff --git a/docs/docs/08_flask_jwt_extended/05_user_model_and_schema/README.md b/docs/docs/08_flask_jwt_extended/05_user_model_and_schema/README.md
@@ -5,12 +5,6 @@ description: Create the SQLAlchemy User model and marshmallow schema.
 
 # The User model and schema
 
-- [x] Set metadata above
-- [x] Start writing!
-- [x] Create `start` folder
-- [x] Create `end` folder
-- [ ] Create per-file diff between `end` and `start` (use "Compare Folders")
-
 Just as we did with items, stores, and tags, let's create two classes for our users:
 
 - The SQLAlchemy model, to interact with the database.
diff --git a/docs/docs/08_flask_jwt_extended/06_registering_users_rest_api/README.md b/docs/docs/08_flask_jwt_extended/06_registering_users_rest_api/README.md
@@ -5,12 +5,6 @@ description: Learn how to add a registration endpoint to a REST API using Flask-
 
 # How to add a register endpoint to the REST API
 
-- [x] Set metadata above
-- [x] Start writing!
-- [x] Create `start` folder
-- [x] Create `end` folder
-- [ ] Create per-file diff between `end` and `start` (use "Compare Folders")
-
 Registering users sounds like a conceptually very difficult thing, but let's break it down into steps:
 
 - Receive username and password from the client (as JSON).
diff --git a/docs/docs/08_flask_jwt_extended/07_login_users_rest_api/README.md b/docs/docs/08_flask_jwt_extended/07_login_users_rest_api/README.md
@@ -5,12 +5,6 @@ description: Learn how to add a login endpoint that returns a JWT to a REST API
 
 # How to add a login endpoint to the REST API
 
-- [x] Set metadata above
-- [x] Start writing!
-- [x] Create `start` folder
-- [x] Create `end` folder
-- [ ] Create per-file diff between `end` and `start` (use "Compare Folders")
-
 Now that we've done registration, we can do log in! It's very similar.
 
 Let's import `flask_jwt_extended.create_access_token` so that when we receive a valid username and password from the client, we can create a JWT and send it back:
diff --git a/docs/docs/08_flask_jwt_extended/08_protect_resources_with_jwt_required/README.md b/docs/docs/08_flask_jwt_extended/08_protect_resources_with_jwt_required/README.md
@@ -5,12 +5,6 @@ description: Use jwt_required from Flask-JWT-Extended to prevent unauthorised us
 
 # Protect endpoints by requiring a JWT
 
-- [x] Set metadata above
-- [x] Start writing!
-- [x] Create `start` folder
-- [x] Create `end` folder
-- [ ] Create per-file diff between `end` and `start` (use "Compare Folders")
-
 Now that our users can sign up and log in, that means we can start _requiring login_ for certain endpoints.
 
 All this means in practice is that the client making the request must send a valid JWT.
diff --git a/docs/docs/08_flask_jwt_extended/09_jwt_claims_and_authorization/README.md b/docs/docs/08_flask_jwt_extended/09_jwt_claims_and_authorization/README.md
@@ -5,12 +5,6 @@ description: Learn how to add claims (extra info) to a JWT and use it for author
 
 # JWT Claims and Authorization
 
-- [x] Set metadata above
-- [x] Start writing!
-- [x] Create `start` folder
-- [x] Create `end` folder
-- [ ] Create per-file diff between `end` and `start` (use "Compare Folders")
-
 JWT claims are extra data we can add to the JWT. For example, we could store in the JWT whether the user whose ID is stored in the JWT is an "administrator" or not.
 
 By doing this, we only have to check the user's permissions once, when we create the JWT, and not every time the user makes a request.
diff --git a/docs/docs/08_flask_jwt_extended/10_logout_users_rest_api/README.md b/docs/docs/08_flask_jwt_extended/10_logout_users_rest_api/README.md
@@ -5,12 +5,6 @@ description: Create a logout endpoint that blocks certain JWTs from making furth
 
 # How to add logout to the REST API
 
-- [x] Set metadata above
-- [x] Start writing!
-- [x] Create `start` folder
-- [x] Create `end` folder
-- [ ] Create per-file diff between `end` and `start` (use "Compare Folders")
-
 To log an user out we must _revoke_ their JWT. That way, if they send us the same JWT again, we can check whether it's been revoked or not. If it has, then we won't authorize them.
 
 To do this, we need a central store of revoked JWTs that we keep around at least until the revoked JWT has expired.
diff --git a/docs/docs/08_flask_jwt_extended/12_token_refreshing_flask_jwt_extended/README.md b/docs/docs/08_flask_jwt_extended/12_token_refreshing_flask_jwt_extended/README.md
@@ -5,12 +5,6 @@ description: Learn about fresh and non-fresh tokens, as well as how to use a ref
 
 # Token refreshing with Flask-JWT-Extended
 
-- [x] Set metadata above
-- [x] Start writing!
-- [x] Create `start` folder
-- [x] Create `end` folder
-- [ ] Create per-file diff between `end` and `start` (use "Compare Folders")
-
 One of the problems with JWT authentication is that JWTs expire, and then the user has to re-authenticate by providing their username and password.
 
 How long to set the JWT expiry time is tricky. If it's very long, it's more likely that a different person may use the same device to access the website, and the previous user's account will still be logged in. If it's very short though, it's really annoying for users.
