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
According to the dec block in the types as well as in the code AbstractNode is a abstract BaseClass. For more semantical expression it should be marked as a abstract class in the type definition.
The text was updated successfully, but these errors were encountered:
bitPogo
changed the title
Should AbstractNode marked as abstract class/interface
Mark AbstractNode as abstract class
Nov 4, 2020
Indeed, even though you cannot really extend AbstractNode or at least that's not the right way to do it since AbstractNode is a Ruby class. So if you want to extend AbstractNode you will need to create a new class with AbstractNode as a superclass using Opal.allocate_class (from Opal runtime):
According to the dec block in the types as well as in the code AbstractNode is a abstract BaseClass. For more semantical expression it should be marked as a abstract class in the type definition.
The text was updated successfully, but these errors were encountered: