Any reason that saves.get was used instead of data.get?

Question

the value is saves.get, in app.py index(), data is stored in saves
any reason that it was not just left as data?

{% extends "layout.html" %}
{% block content %}
        <form action="{{url_for("save")}}" method="POST"><!--action, method-->
            <label>Name your bear</label><!--abovinput-->
<!-- the value is saves.get, in app.py index(), data is stored in saves-->
<!-- any reason that it was not just left as data? -->
            <input type="text" name="name" value= "{{saves.get("name", '')}}" autofocus><!--enter-->
            <input type="submit" value="Let's build it!"><!--button-->
        </form>

{% endblock %}

app.py

import json
from flask import Flask 
from flask import (render_template, redirect, url_for, request,
                  make_response)

app = Flask(__name__)

def get_saved_data():
  try:
    data = json.loads(request.cookies.get("character"))
  except TypeError:
    data = {}
  return data

@app.route("/")
def index():
  data = get_saved_data()
# here, data is stored as saves.  
# Seems like it could have just been left as data
  return render_template("index.html", saves=data)

@app.route("/save", methods=["POST"])#only accessible with POST
def save():
  response = make_response(redirect(url_for("index")))
  data = get_saved_data()
  data.update(dict(request.form.items()))
  response.set_cookie("character", json.dumps(data))
  return response


app.run(debug=True, host="0.0.0.0", port=8000)import json

john larson

john larson

Any reason that saves.get was used instead of data.get?

Juan Suarez

Juan Suarez