allow unknown properties

since the scripting API can define new properties and we (for now) do
not know what the script may or may not be able to do, the linter would
otherwise reject potentially valid maps.

1 files changed, 2 insertions, 11 deletions

diff --git a/lib/Properties.hs b/lib/Properties.hs
index 35cc155..5720f42 100644
--- a/lib/Properties.hs
+++ b/lib/Properties.hs
@@ -252,17 +252,8 @@ checkLayerProperty p@(Property name _value) = case name of
         False -> warn "property \"collides\" set to 'false' is useless."
     "name" -> isUnsupported
     -- all properties relating to scripting are handled the same
-    _ | name `elem` [ "default"
-                    , "readableBy"
-                    , "writableBy"
-                    , "persist"
-                    , "jsonSchema"
-                    , "zone" ] ->
-        do
-          warn "the workadventure scripting API and variables are not (yet?) supported."
-          removeProperty name
-      | otherwise ->
-        complain $ "unknown property type " <> prettyprint name
+    _ ->
+        warn $ "unknown property type " <> prettyprint name
     where
       isForbidden = forbidProperty name
       requireProperty req = propertyRequiredBy req name