git-reconcile-rewritten-list

words:	3 + 218 = 221
last update:

#public
parent:: [[git-stacked-rebase]]

Linked Mentions (1 in 1 page)

May 7th, 2022 (1)
- {{[[DONE]]}} actually, this is becoming an extraction of setting up the `post-rewrite` hook, and thus actually an extraction into [[git-reconcile-rewritten-list]]!
  - #observation [[(hidden) q5DIUyEP-]] when you have code like this:
    - ```typescript function wrapper() { prerequisiteForA() return A() } function prerequisiteForA() { foo() } function A() { bar() } ```
    - you could and probably should have it like this:
      - ```typescript function A() { prerequisiteForA() bar() } function prerequisiteForA() { foo() }```
    - it should become even more obvious when you start taking in the same or similar args in `wrapper` to forward them to `A`. same with creating similar or identical types.
    - e.g. b4 & after:
      - https://github.com/kiprasmel/git-stacked-rebase/commit/0a7eac20e8fb1f0566283355bd18568f1ccfc3fe
      - https://github.com/kiprasmel/git-stacked-rebase/commit/0a09085b214ad8fb05e39b1832ee0012657663d9
  - {{[[TODO]]}} #[[(hidden) jOMmlCP4S]] [[git]] or maybe more like [[codemods]] -- have a way to sort the order in which your functions are placed by DFS
    - i.e. the main function A is at the top. the 1st used one B is right below it, the one inside B is right below it, etc
    - just feels like the right way to structure things.
      - w/o getting into splitting into separate files yet
        
        tho, if your file only exports 1 main fn, and has others non-exported (tho meh) or imported from other util files (maybe, tho would prefer if they lived inside a folder specific to this file), then it might be the right thing.
        
        idk, gotta think & explore more
        
        also thoughts about [[(hidden) Q8L4MEUSD]]'s [[destiny]] project