| Age | Commit message (Collapse) | Author |
|---|
|
ill-defined -- if a parser only parses a partial document via include, there may be many to no nodes that are returned). Parsers should just use the ParserScope.push funciton. All nodes pushed onto the top-level of the ParserScope are added treated as the nodes the parser has parsed. Adapted all code and all tests accordingly.
|
|
|
|
reduces coupling and was stupid beforehand.
|
|
|
|
|
|
|
|
|
|
gave a ResourceManager instance to the Project, using ResourceRequest when including or linking files, thought through how "including" and "linking" are handled
|
|
|
|
class and corresponding (unfinished) test
|
|
compatible with the Variant cardinality.
|
|
reading tests.
|
|
|
|
|
|
|
|
|
|
|
|
SourceContextReader interface in ResourceManager, added LoggerTest
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
namespace, added new functionality to RegistryClass, wrote documentation, added function for extracting file extensions to Utils
|
|
|
|
|
|
StaticResourceLocator which can be used for registering static resources (mainly for testing or if certain resources need to be available from the executable)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
tests are required, though.
|
|
|
|
|
|
|
|
protected methods
|
|
(to prevent Manager empty assertion to fail)
|
|
|
|
|
|
to be reusable after a move. Adapted unit test accordingly.
|
|
|
|
|
|
|
