Merge pull request #57 from sachbearbeiter/main

Fix #56

Author: sachbearbeiter

README.md

@@ -16,6 +16,7 @@ Note that this Composer package name (belugadigital/kirby-navigation) differs fr
 | Kirby version | Compatible plugin version |
 |:--------------|:--------------------------|
 | ^5.0          | ^5.0                      |
+| ^4.8          | ^4.2                      |
 | ^4.0          | ^4.0                      |
 | ^3.7          | ^3.0                      |
 | ^3.6          | ^2.0                      |
@@ -161,6 +162,10 @@ If you want to add an anchor value to your 'Kirby page' links, for example to ha
 
 If you use the recommended way to output the navigation markup from your template (such as $site->navigation()->toNavigationMarkup() in case of a field called 'navigation'), then any target, class and anchor values will be included automatically in the generated markup.
 
+## What's new in version 5.0?
+
+Works with Kirby 5.0
+
 ## Contributing
 
 Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

composer.json

@@ -8,7 +8,7 @@
     "menu",
     "field"
   ],
-  "version": "5.0.0",
+  "version": "5.0.1",
   "license": "MIT",
   "homepage": "https://github.com/chrisbeluga/kirby-navigation",
   "authors": [

config/props.php

@@ -31,7 +31,8 @@
       // Add a 'save' item. When the 'props' values are sent to Panel,
       // the Field.vue will hide this item, but it will send it back,
       // and then the props.php will detect it, and save.php will ignore it.
-      $items[]=['type' => 'save', 'uuid' => uniqid(), 'children' => []];
+      // Use a constant uuid value for this item, to avoid diff problems
+      $items[]=['type' => 'save', 'uuid' => 'save', 'children' => []];
     }
     return $items;
   },