Principles of Anvil Version Control for Dummies

Anvil Q&A
1

I see a common thread to every topic in (Unofficial) Anvil Version Control for Dummies

  1. Identification of a specific feature that varies from one [version of an] app to another.
  2. Identification of the source-code-level artifacts that go into that feature (app feature or Anvil feature), and where they can be found. In some files, these are just a fragment of the entire file.
  3. Using 2 to manage those artifacts, especially when Anvil’s default management does not do what’s appropriate in your specific case. This includes defining extra steps to perform, before and/or after an Anvil or Git action.

Do I have this abstracted properly?

1 Like
2

5 posts were merged into an existing topic: (Unofficial) Anvil Version Control for Dummies