This PR is the result of a review of Easy EdgeDB from top to bottom as if encountering the book for the first time. It contains the largest structural changes of any PR so far so is the one that brings the book closest to a version 2.0.
Planned future PRs to officially bring the book to what I'd consider 2.0 status are going to be delayed for some time but will end up being as follows:
"Feature complete" PR: look through every corner of the documentation to see what is missing and should be in the book
Chapter restructuring: some chapters have gotten quite large and the book could probably be made into 25 chapters instead of the current 20. Then once that is done:
Interactivity à la the EdgeDB tutorial. Probably will make a single schema with one module per chapter to make this happen.
Finally, some design and related touching up.
But pretty satisfied with the changes in this PR in the meantime as it makes some changes to parts of the book that I've been least satisfied with and brings a larger focus on the idea of putting a game together. There are a lot of changes to the PC type for example, including imaginary user account info followed by a trigger that removes an imaginary customer's personal data but inserts another object at the same time that includes the minimum amount of information to restore an account if necessary. Feels a bit more like a real life scenario.
This PR is the result of a review of Easy EdgeDB from top to bottom as if encountering the book for the first time. It contains the largest structural changes of any PR so far so is the one that brings the book closest to a version 2.0.
Planned future PRs to officially bring the book to what I'd consider 2.0 status are going to be delayed for some time but will end up being as follows:
But pretty satisfied with the changes in this PR in the meantime as it makes some changes to parts of the book that I've been least satisfied with and brings a larger focus on the idea of putting a game together. There are a lot of changes to the PC type for example, including imaginary user account info followed by a trigger that removes an imaginary customer's personal data but inserts another object at the same time that includes the minimum amount of information to restore an account if necessary. Feels a bit more like a real life scenario.