You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, any AsyncNode objects encountered in content won't be parsed as player specific node types as there is no definition for it in the LSP parser here nor logic in the parse function here that will create it as a specific node type. That means that it will just be treated as an ObjectASTNode. While this won't cause any content validation issues, it does mean that validation rules can't be written against AST Nodes. One such validation would be ensuring that all Async Nodes have unique IDs as that will cause issues at runtime. This would function similarly to the existing DuplicateIDPluginhere.
TO DO
Define an AsyncASTNode type
Update parsing logic to identify and create AsyncASTNodes
Create new 1st party validator to validate unique AST node id properties
The text was updated successfully, but these errors were encountered:
Background
Currently, any
AsyncNode
objects encountered in content won't be parsed as player specific node types as there is no definition for it in the LSP parser here nor logic in theparse
function here that will create it as a specific node type. That means that it will just be treated as anObjectASTNode
. While this won't cause any content validation issues, it does mean that validation rules can't be written against AST Nodes. One such validation would be ensuring that all Async Nodes have unique IDs as that will cause issues at runtime. This would function similarly to the existingDuplicateIDPlugin
here.TO DO
AsyncASTNode
typeAsyncASTNode
sid
propertiesThe text was updated successfully, but these errors were encountered: