From 4da3923a3c57bd14c06e3020e529c34be9b87e1e Mon Sep 17 00:00:00 2001
From: Thomas Anagrius <anagrius@users.noreply.github.com>
Date: Thu, 3 Dec 2020 19:54:18 +0100
Subject: [PATCH] Don't treat Nav Key to move as an error

Allowing the navigation key to move was fixed earlier,
but it never actually worked in practice. The change of
path was still treated as an error condition.
---
 resources/hmr.js | 2 --
 1 file changed, 2 deletions(-)

diff --git a/resources/hmr.js b/resources/hmr.js
index 0be0fd2..7293bc6 100644
--- a/resources/hmr.js
+++ b/resources/hmr.js
@@ -423,8 +423,6 @@ if (module.hot) {
                             error = "could not find Browser.Navigation.Key in the new app model";
                         } else if (oldKeyLoc === null) {
                             error = "could not find Browser.Navigation.Key in the old app model.";
-                        } else if (newKeyLoc.keypath.toString() !== oldKeyLoc.keypath.toString()) {
-                            error = "the location of the Browser.Navigation.Key in the model has changed.";
                         } else {
                             // remove event listeners attached to the old nav key
                             removeNavKeyListeners(oldKeyLoc.value);