scenarios for the on-disk representation

[?]
Jan 25, 2023, 4:28 PM
MOUXJ6VT5YQABAMPBAEABJHGIVQLQ4X7UPBIUVINK4KWD2SWAPXAC

Dependencies

Change contents

  • edit in representation.md at line 56
    [2.1779]
    # Scenarios considered in designing this representation
    * Capture history of changes.
    - Though it is perhaps too fine-grained and noisy.
    * Merge changes from non-live forks to live ones.
    - New files in repo can't hide changes in save dir, because filenames are
    always disjoint between the two.
    - This doesn't apply yet to live updates. Two forks of a single live app
    will likely have unnecessary merge conflicts.
    * No special tools required to publish changes to others.
    - Just move files from save dir to repo.
    # Scenarios I _would_ like to take into consideration in the future
    * Cleaner commits; it's clear what changed.
    * merge changes between live forks.