elm-hot
elm-hot copied to clipboard
Don't treat Nav Key to move as an error
About a year ago an issue was fixed where moving the Navigation Key in the application Model would make Hot Reloading fail. While the logic to detect the new location of the key was implemented, the code still seems to treat the move as an error condition.
The fix was in 1.1.4
:
fixed a bug where HMR failed because Browser.Navigation.Key changed location
It seems that the check for what was previously considered an error is still in place. This PR will remove that check and just update the key.
bump?
bump
bump?
bump? :..(