The Life Starter
0 of 6 complete0%
Course Library · Lesson 5 of 6
Digital · Guided lesson

Import without trusting the file name

About 29 minutes · 7 reading + 22 practice and checks
Time includes reading, practice, and questions. Extra videos or further study are optional.
See this course’s project requirements

A fictional local reading-list app with versioned saved data, explicit browser-only wording, validated JSON export/import and corrupt-save recovery tests.

Keep your working files in your own notebook or software. Save a private description, checklist, and work link in My Proof.

What to include

  • Document the exact storage origin and distinguish reload persistence from account synchronization.
  • Retain the validated envelope format and prove an invalid replacement leaves the earlier record intact.
  • Demonstrate a rejected corrupt load and a failed write without silently discarding prior data.
  • Create and inspect an actual JSON export and state its exact contents.
  • Produce a valid/invalid import matrix proving rejected content retains the previous list.
  • Deliver a two-tab observation or truthful unavailable note, alongside the validated backup/recovery project.

Review and revise

Use these criteria to check your work and choose what to improve.

  • The implementation or declared simulation follows the supplied contract and retains inspectable original inputs.
  • Normal, boundary and rejected cases are recorded with expected versus observed results.
  • The changed case has a correct explanation and does not rely on hidden state.
  • The project includes source, outputs, instructions and honest tool, privacy and verification limits.
Open the full course project
Want more background?
Before you begin

The idea in everyday life

Use the supplied reading.html, reading-store.mjs and test-reading.mjs with the invented title Moon Garden. Serve the folder at http://localhost:8765 using python3 -m http.server 8765 --bind 127.0.0.1.

The idea

A JSON file extension is a hint, not validation. The import must parse, check size and schema, and save successfully before replacing the current memory list.

Follow along

Import without trusting the file name — original worked practice

A JSON file extension is a hint, not validation. The import must parse, check size and schema, and save successfully before replacing the current memory list.

Use the supplied reading.html, reading-store.mjs and test-reading.mjs with the invented title Moon Garden. Serve the folder at http://localhost:8765 using python3 -m http.server 8765 --bind 127.0.0.1.

  1. 1. Step 1

    Copy the exported JSON and change Moon Garden to River Map while keeping version 1 and a valid revision. Import that file.

    You should see: The validated River Map list replaces memory only after a successful save.

    A JSON file extension is a hint, not validation. The import must parse, check size and schema, and save successfully before replacing the current memory list.

  2. 2. Step 2

    Create a second file with version 2 and attempt import.

    You should see: The unsupported import is rejected.

    A JSON file extension is a hint, not validation. The import must parse, check size and schema, and save successfully before replacing the current memory list.

  3. 3. Step 3

    Compare the list after rejection with the River Map list.

    You should see: The valid previous list is retained.

    A JSON file extension is a hint, not validation. The import must parse, check size and schema, and save successfully before replacing the current memory list.

  4. 4. Step 4

    Retain both files and an expected/observed import matrix; use no private document data.

    You should see: A valid/unsupported import test record.

    A JSON file extension is a hint, not validation. The import must parse, check size and schema, and save successfully before replacing the current memory list.

Now change one thing

A .json file contains invalid text {. Does its extension make the import valid?

Your work

What to finish

Produce a valid/invalid import matrix proving rejected content retains the previous list.

Common mistake

Watch for this

Trusting the .json extension or replacing the draft before the storage write succeeds.

How can I tell I understand it?

Demonstrate the rule: A JSON file extension is a hint, not validation. The import must parse, check size and schema, and save successfully before replacing the current memory list. Use the supplied variant to distinguish a changed result from a broken implementation.

Try 3 questions

Quick knowledge check

Answer all 3 questions. Get at least 2 right and the lesson completes automatically.

Not yet passed

You’ll get an explanation for each answer. Signed in? Your results save to your account.

1A file is named backup.json but contains {. What should happen?
2Which import stage must finish before memory replacement?
3Why limit this import file to 10000 bytes?
0 of 3 answeredApply the lesson to a short question, then review the explanation.
5
Finish this lesson

Pass the check. We’ll save the progress.

Answer all 3 questions above and get at least 2 right. You can review the explanations and try again.

Go to the knowledge check
Tools, templates, and lesson sources

Tools and templates

Tools open in a new tab so you can keep your place here.

Sources and further reading

Explore the references behind this lesson.

developer.mozilla.org — localStorage
Source & access notes · checked 2026-10-01

Relevant documented module/API behavior inspected during expansion authoring; actual execution evidence is recorded separately. No grant eligibility is established.

Access: Official page retrieved with the web reader on 2026-10-01. Documentation reading does not certify execution in every native tool or browser.

Reuse: Original local practice files, fictional data, worked examples and questions. Concepts paraphrased and linked; source exercises are not copied.

developer.mozilla.org — Blob
Source & access notes · checked 2026-10-01

Relevant documented module/API behavior inspected during expansion authoring; actual execution evidence is recorded separately. No grant eligibility is established.

Access: Official page retrieved with the web reader on 2026-10-01. Documentation reading does not certify execution in every native tool or browser.

Reuse: Original local practice files, fictional data, worked examples and questions. Concepts paraphrased and linked; source exercises are not copied.

Report a problem with this lesson

Tell us what went wrong. Please leave out personal information and private project contents.

No sign-in needed.