BUGFIX: Allow other value types for property migrations

Resolves: #22
Sebobo · Feb 14, 2024 · f765ed4 · f765ed4
1 parent a495790
commit f765ed4
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 1 deletion.
diff --git a/NodeMigration.Schema.json b/NodeMigration.Schema.json
@@ -327,7 +327,11 @@
                                 "newValue": {
                                     "description": "New property value to be set.\n\nThe value of the option currentValuePlaceholder (defaults to “{current}”) will be used to include the current property value into the new value.",
                                     "x-intellij-html-description": "<p>New property value to be set.\n\nThe value of the option <code>currentValuePlaceholder</code> (defaults to “{current}”) will be used to include the current property value into the new value.</p>",
-                                    "type": "string"
+                                    "type": [
+                                        "string",
+                                        "number",
+                                        "boolean"
+                                    ]
                                 },
                                 "search": {
                                     "description": "Search string to replace in current property value.",

diff --git a/examples/Version20140708120530.yaml b/examples/Version20140708120530.yaml
@@ -18,6 +18,11 @@ up:
         -
           type: 'MyCustom'
           settings: []
+        -
+          type: 'ChangePropertyValue'
+          settings:
+            property: 'myBooleanProperty'
+            newValue: false
     -
       filters:
         -