(hidden) wJyVZW0Tm

words:	0 + 333 = 333
last update:

Linked Mentions (1 in 1 page)

November 3rd, 2021 (1)
- {{[[TODO]]}} #[[(hidden) jOMmlCP4S]] re: [[(hidden) wJyVZW0Tm]]
  - https://danburzo.ro/javascript-codemods/
  - we could have a pre-processing transform that would collect all imports, exports and wraps around our components, and then use that output inside the transforms that rely on that information!
  - {{[[TODO]]}} need to specify transform dependencies inside transform
    - ```javascript export const dependencies = [transformA, transformB]```
  - {{[[TODO]]}} need [[(hidden) vkt9VljJ3]] for transforms, and to run each sub-level sequentually in the codeshift-cli.
    - would _not_ be needed if ... will be needed.
  - each transform would get an additional arg - `outputsFromDependencies`, and would use `outputsFromDependencies[transformFnThatGeneratedThatOutput]` to access the specific outputs
    - {{[[TODO]]}} and each transform would return not only the modified source, but also the outputs.
    - idea taken exactly from [[roam-traverse-graph]] :D
  - {{[[TODO]]}} update template to `export const myTransform: Transform = () => ...`
    - {{[[TODO]]}} add `export const dependencies: TransformDependencies`
    - {{[[TODO]]}} validate w/ validator
      - https://github.com/CodeshiftCommunity/CodeshiftCommunity/blob/f79407a95d823d01e0b9b3928397f47c7f81c556/packages/validator/src/index.ts
      - https://github.com/CodeshiftCommunity/CodeshiftCommunity/blob/506fa08c8cda2782d3153cada23530eec965b727/packages/cli/src/validate.ts
  - sidenote / #observation - #[[(hidden) DY6wPnICE]] there's so much #[[(hidden) K0RqswvNf]]!
    - (hidden) jZqNG3dcZ
    - {{[[TODO]]}} (hidden) p4cFDB07K [[(hidden) v8hKA88Fi]] #[[(hidden) bqn786OaX]]
  - likely will need to use recast or whatever lower level lib & read file contents w/ fs to be able to traverse full graph.
    - i. e. find all files that import e. g. a button from cui
    - then, for each file, find what wraps it - other elements, styled, etc
    - check if the wrapper are exported
      - no: add but only applicable inside that file
      - yes:
        
        will need to create a normalized (like yarn lockfile instead of npm's) map of what absolute path imports what absolute paths
        
        from that map, find where the wrap is imported from
        
        note - maybe better to have a transform that just for each file it goes thrue, it adds to the normalized array that file, all imports and all exports.
        
        this way walking and filtering would be simpler