Skip to content
Snippets Groups Projects
Commit f1c6de8f authored by stuebinm's avatar stuebinm
Browse files

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.
parent 72d66169
No related branches found
No related tags found
No related merge requests found
...@@ -252,17 +252,8 @@ checkLayerProperty p@(Property name _value) = case name of ...@@ -252,17 +252,8 @@ checkLayerProperty p@(Property name _value) = case name of
False -> warn "property \"collides\" set to 'false' is useless." False -> warn "property \"collides\" set to 'false' is useless."
"name" -> isUnsupported "name" -> isUnsupported
-- all properties relating to scripting are handled the same -- all properties relating to scripting are handled the same
_ | name `elem` [ "default" _ ->
, "readableBy" warn $ "unknown property type " <> prettyprint name
, "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
where where
isForbidden = forbidProperty name isForbidden = forbidProperty name
requireProperty req = propertyRequiredBy req name requireProperty req = propertyRequiredBy req name
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment