6 ms·

There was a similar project to `go fix` with elm-upgrade (https://github.com/avh4/elm-upgrade https://github.com/avh4/elm-upgrade). We migrated a ~100k LOC app

by antew 5y ago

There was a similar project to `go fix` with elm-upgrade (https://github.com/avh4/elm-upgrade https://github.com/avh4/elm-upgrade). We migrated a ~100k LOC app at work from 0.18 to 0.19 and while it was tedious, the compiler really has your back and makes it easier. We weren't bit by the removal of native/kernel code, but it definitely turned a lot of people away that may have been committed to Elm before.

girishso 5y ago
True that. We also ported our Elm codebase from 0.18 to 0.19. It took us almost a week working almost 24/7 across two timezones to make the damn thing compile again. Did not see the UI for the entire week, but once it compiled it (mostly) just worked like nothing had changed (that's after 429 files changed, 16422 insertions(+), 12116 deletions(-)). My colleague took notes of the progress at https://gist.github.com/mordrax/efcd34739ed56bb64d2b12d2401b7291 https://gist.github.com/mordrax/efcd34739ed56bb64d2b12d2401b...
- savanaly 5y ago
  Wow! Apologies if this is answered in those notes but my quick question is: Did you make extensive use of Debug.todo to cordon off sections of the app that wouldn't compile in order to work on and "see" the other sections in the meantime? That's what I do on my small elm apps, e.g. put whole features or functionality behind Debug.todos.
  - girishso 5y ago
    I might be wrong but I think Debug.todo was introduced in Elm 0.19. But in any case we were not aware of it at the time and didn’t use it. Btw Debug.todo is amazing and we do use it now sometimes.
- b3morales 5y ago
  From the gist: > We have until Friday 7th September to upgrade to Elm 0.19. I'm completely ignorant about the transition, but I'm curious what the source of this deadline was. Would you mind expanding?
  - girishso 5y ago
    Basically business didn’t see any benefits of spending time on the upgrade, time that could be used to improve/add features to the product.
- mjaniczek 5y ago
  I remember hearing Mordrax speak about the upgrade, quite herculean! At our company it was much less drastic. At the time we had about 35kloc of Elm and it took me one evening of Vim macro frenzy. The trickiest things we encountered were an elm/http API change and temporarily vendoring packages that didn't yet upgrade themselves.

by antew 5y ago

girishso 5y ago

True that. We also ported our Elm codebase from 0.18 to 0.19. It took us almost a week working almost 24/7 across two timezones to make the damn thing compile again. Did not see the UI for the entire week, but once it compiled it (mostly) just worked like nothing had changed (that's after 429 files changed, 16422 insertions(+), 12116 deletions(-)). My colleague took notes of the progress at https://gist.github.com/mordrax/efcd34739ed56bb64d2b12d2401b7291 https://gist.github.com/mordrax/efcd34739ed56bb64d2b12d2401b...

savanaly 5y ago
Wow! Apologies if this is answered in those notes but my quick question is: Did you make extensive use of Debug.todo to cordon off sections of the app that wouldn't compile in order to work on and "see" the other sections in the meantime? That's what I do on my small elm apps, e.g. put whole features or functionality behind Debug.todos.
- girishso 5y ago
  I might be wrong but I think Debug.todo was introduced in Elm 0.19. But in any case we were not aware of it at the time and didn’t use it. Btw Debug.todo is amazing and we do use it now sometimes.
b3morales 5y ago
From the gist: > We have until Friday 7th September to upgrade to Elm 0.19. I'm completely ignorant about the transition, but I'm curious what the source of this deadline was. Would you mind expanding?
- girishso 5y ago
  Basically business didn’t see any benefits of spending time on the upgrade, time that could be used to improve/add features to the product.
mjaniczek 5y ago
I remember hearing Mordrax speak about the upgrade, quite herculean! At our company it was much less drastic. At the time we had about 35kloc of Elm and it took me one evening of Vim macro frenzy. The trickiest things we encountered were an elm/http API change and temporarily vendoring packages that didn't yet upgrade themselves.