November 29th, 2021

{{[[TODO]]}} soon, ping again [[(hidden) v8hKA88Fi]]

{{[[TODO]]}} yes do

{{[[TODO]]}} and review tomorrow w/ [[(hidden) tv1zOVzED]]

LP

{{[[TODO]]}} inform LP lead

{{[[DONE]]}} extract into separete commit re-exports

{{[[DONE]]}} drop & verify works

{{[[DONE]]}} move the `codemod.ts` commit before the 1st transform, split into needed & move all others into separate commit

{{[[DONE]]}} probably amend into the transform commit -> yes

{{[[DONE]]}} move the separate commit up until the 2nd transform

{{[[DONE]]}} repeat

{{[[TODO]]}} when done, test each ~~commit~~ PR

{{[[TODO]]}} actually submit & merge into upstream #[[(hidden) k27EB-_6T]]

{{[[TODO]]}} hide slack from ~1h 9m 30s just in case, idk

{{[[TODO]]}} make public

```shell git branch ```

1.1 make sure this is actually the one you want to rebase.

1.2 am i the only one working on this branch?

```shell # while inside the same (your own) branch: git pull ```

if you see something unexpected, there's probably changes from someone else, thus you answer "no" to [1.2](((PBP6PdUmS))), thus abort (unless ofc you know what you're doing).

```shell git fetch --all ```

```shell git rebase origin/master -i ```

`-i`, or `--interactive`, will bring up the list of commits of your branch. you can view it to confirm everything's alright, and if not, you can squash/fixup/drop, even re-order the commits. basically, become a surgeon for a bit.

but if often does not.

you can always use `git status` to see what's going on

in case you encounter conflicts:

there are some edge cases as well

if you check `git status`, it'll show that you have more commits ahead and less commits behind. makes sense, since you previously had only your commits that you started from an older commit of the master branch, but you now have all of that, plus the new commits from the master branch that you were missing.

since we overwrote history, a regular `git push` won't do (you can try). you'll need to force it with `-f` or `--force`:

```shell git push -f ```

`git reflog` is your friend:

glhf. if you're a newbie w/ this stuff, consider copying the `.git/` folder outside the repo `../` in case you need to start from scratch.

talking w/ an experienced colleague / friend also helps.

rebase goes commit-by-commit (1 by 1)

it's easy to mess things up.

it's always better to do simple changes in multiple rebases, than multiple complex changes in a single rebase.

install nvm

then

so maybe the choice for which marking means which behavior can be changed, or we can have exceptions, or maybe #roam can make it configurable what alias you insert, but anyhow, that's less relevant / can think of it in the future.

the point is that this seems useful

{{[[DONE]]}} misc: just submitted a different #[[(hidden) D1lY0CG5e]] - to allow control/ctrl+enter (or whatever binding) to create a new block in the same level, even if the current one is empty

e.g. https://ts.kipras.org/Adomaitis%20Vilius/2#[[(hidden) G97ohL3l8]]lesson-2-7 (must be in mobile view atm xd)

(idea from stackoverflow, ofc)

```typescript export type FromToValueMap = { [key in ValidJsxPropertyValueAsKey]?: | ValidJsxPropertyValueAsValue | FromToValueMapModifierFn /** * otherwise, provide an array of new values. * * if array contains exactly 1 element: * will replace the value automatically; * * else, if array contains >1 element: * will replace the value with the 1st one from the array, and * will add a comment, prefixed with "TODO CODEMOD MANUAL INTERVENTION", to make the user verify themselves. */ | ArrayWithAtLeastOneElement<ValidJsxPropertyValueAsValue>; };```

went w/ the initial solution - advanced function overload, and in typescript for both functions allowed to return either a number or a boolean, and implemented runtime typeof checks to throw errors if incorrect type returned.

ideally #typescript fixes this & we can use the original solution w/o having to have runtime assertions.