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, the script checks if modules and functions are present. However, since Löve2D is object-oriented, the functions defined inside the tables returned by the newXXX functions are also part of the API. (or in other words, the methods on the objects returned by the constuctor functions).
Currently, the script does not check if methods are present. This requires work as it is needed to instanciate a type to check if its methods are present or missing.
When checking a type, the script should:
check if the type has a constructor
check the constructor definition (to check for a suitable variant to call)
call the constructor
check if the methods are present
check if the methods of the supertypes are present
Since a constructor may need other objects to be called, it may not be possible to do the 3rd step automatically from the api description for all types. Those types could be checked with manual code for the instanciation.
The 5th step requires to build a dictionnary of the types defined by the API, as the documentation is written as a tree and not as a map.
The text was updated successfully, but these errors were encountered:
Currently, the script checks if modules and functions are present. However, since Löve2D is object-oriented, the functions defined inside the tables returned by the newXXX functions are also part of the API. (or in other words, the methods on the objects returned by the constuctor functions).
Currently, the script does not check if methods are present. This requires work as it is needed to instanciate a type to check if its methods are present or missing.
When checking a type, the script should:
Since a constructor may need other objects to be called, it may not be possible to do the 3rd step automatically from the api description for all types. Those types could be checked with manual code for the instanciation.
The 5th step requires to build a dictionnary of the types defined by the API, as the documentation is written as a tree and not as a map.
The text was updated successfully, but these errors were encountered: