We have to check, whether import uri validation throws errors although our include resolution works properly. If this is the case, the default validator should be replaced by a custom one, taking the adapted resolution into account. (See #122)
This should be fixed with #151. If an include could not be resolved by the LilyPondImportUriResolver, it will be prefixed by a marker, indicating such a file does not exist.
We have to check, whether import uri validation throws errors although our include resolution works properly. If this is the case, the default validator should be replaced by a custom one, taking the adapted resolution into account. (See #122)