You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We started using elm-html 4.0.0 for our prod code, but now our tests break because elm-check requires 3.0.0 - even though we aren't using elm-check's HTML reporting!
It seems like the HTML reporting should be a separate, decoupled package to prevent this. Otherwise it will be either a constant need to upgrade immediately to the latest elm-html (even when there's no need) or else compatibility will continue to break for users who aren't even using the html output.
Thoughts?
The text was updated successfully, but these errors were encountered:
We started using elm-html 4.0.0 for our prod code, but now our tests break because
elm-check
requires 3.0.0 - even though we aren't using elm-check's HTML reporting!It seems like the HTML reporting should be a separate, decoupled package to prevent this. Otherwise it will be either a constant need to upgrade immediately to the latest elm-html (even when there's no need) or else compatibility will continue to break for users who aren't even using the html output.
Thoughts?
The text was updated successfully, but these errors were encountered: