The problem was with recent addition of templates path handling. An exception is raised if no valid template path is found. However as validation message needs to be sent before the main application handling method due to how DDCli works, exception was raised before we handled any setting. This effectively required the user to pass in a valid templates path even just to see help or version...
… version to beta...
This is useful for debugging mostly.
Reasoning is similar to previous commit.
…ng protocol. Instead, the GBApplicationSettingsProvider class is used. Objective-C can solve "program to interface" rule quite easily through anonymous type and we can as easily mock classes as we can protocols, so having a protocol only complicated development...
…opyWithZone: to make it more robus. The main reason for adding company identifier is to reuse it for documentation set bundle and publisher identifiers. The more robust unit test mentioned uses customly crafted expected string instead of simply getting it from settings object. This allows proper testing that all templates placeholders are actually being handled by the code!
This will be used for handling settings levels shortly - factory defaults, global parameters, command line arguments.
… placeholder strings and which placeholder strings are available.
These are required so that we can suppress certain options that are on by default - DDCli only sets booleans to YES, so implementation is kind of duplicative - we need to add additional prefixed option for each boolean option.
… unit tests.
…lation. This would work better during testing.
…oval of undocumented objects. Due to the fact that we may copy documentation from superclasses, we must remove undocumented members and objects only after processing members, otherwise we would delete overriden methods before getting the chance to copy the documentation.
At this point a single section is created and all methods registered to it.
At this point we simply remove the category without actually merging as we're only testing merging on/off switch.
This was completely forgotten. As the path was not written, docsetutil validate resulted in exception and clicking on search results in Xcode resulted in errors. Thanks to these I finally discovered the empty <File path=""> element in generated tokens files...
…viding to encapsulate replacements for it's values. This simplifies the rest of the application, reduced code clutter and speeds up as these values don't change during the run!
…lity to GBApplicationSettingsProviding objects.