All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and it was adapted for the curriculum repository.
Format
The general format is:
## Date
### Type of change
- [Topic Name - Insight Name - Description of the change](link-to-the-PR-or-commit-where-the-change-was-added)Date represents the date on which the PR was merged.
If more than one insight is changed in the PR, you can:
- use the workout name with an appropriate description
- [Topic Name - Workout Name - Description that applies to all insights changed](link-to-the-PR-or-commit-where-the-change-was-added)- write an entry for each insight using the same PR link:
- [Topic Name - Insight Name 2 - Description](link-to-the-PR)
- [Topic Name - Insight Name 1 - Description](link-to-the-PR)Types of change:
Addedfor new content (e.g. a new insight, workout, topic).Changedfor changes in the existing content (e.g. changing the concepts or structure of an existing insight).Archivedfor content that is no longer necessary and has been archived.Fixedfor any minor fixes (e.g. add a missing comma, adding a code block tag, fixing a report).
- TypeScript - Number, String & Boolean - Retrigger footnotes
- Python - Python Variables - Add footnotes back
- SQL - What is SQL - Add footnotes back
- Python - Python Variables - Temporarily removed footnotes
- SQL - What is SQL - Temporarily removed footnotes
- SQL - What is SQL - Fix typo in footnote
- SQL - Why Learn SQL - Remove old paragraph
- Python - Boolean Operators - Fix typo
- Python - What Are Decorators? - Fix minor grammatical mistakes
- Python - List Methods II - Fix last code block example
- Python - List Methods I - Fix resource link
- React -
React.Childrenmethods - Remove duplicate "returns" - Python - Variables - Add missing "i" in "revist"