Clone this repo: https://github.com/bigardone/elm-css-patterns/blob/master/elm.json
- Setup
elm-review
rule for quick edit/feedback cycle
-
De-dupe ranges
-
Get a sense of scope: how many lines per module
-
Find/collect problematic cases
- non-primitive/dynamic values / free variables
-
AST? representation
-
Further analyze: how many instances are very simple
- What recorded format? JSON? can we then load JSON in
elm-review
and use that to inform fixes? - AI somehow???
Observable notebook of actual code https://observablehq.com/d/5480a664b168012a
(make a copy of this for elm-css-patterns
)
Maybe use this for inspo https://github.com/dillonkearns/elm-css-transpiler-demo/