http://bugzilla.qooxdoo.org/show_bug.cgi?id=7182
But without that, a good pattern is to silence these warnings for 'api',
... jobs that involve other libraries (including the framework), but have
it on for the 'lint' job as it only inspects the current lib, so you get
your own typos etc.
T.
>>> [...]
>>
>> Add an "api" job to your config.json and provide it with a "lint-check"
>> key like this:
>>
>> "api" : {
>> "lint-check" : {
>> "warn-unknown-jsdoc-keys" : false
>> }
>> }
>>
>> [...]
>>
>> Alternatively (if you want to silence it for multiple applications at
>> once), edit component/apiviewer/api.json:
>>
>> "warn-unknown-jsdoc-keys" : false,
>
>
> Thank you for the info. But wouldn't this also silence any misspelled
> JsDocs in
> the 'broader scope' (whole application)? I can imagine that I accidentally
> type "@assert(" instead of "@asset(" sometimes in the future ;) And it
> would
> be nice if the generator would still be able to notify me.
> Or will I be warned about those during "source" or "build"?
>
> It would be nice if this could be narrowed to just the module/namespace
> that's having those unknown doc keys (here: Sinon.js). Like it is done at
> "let/API_EXCLUDE" feature.
>
> Thanks again,
> Peter
> --
>
> ***********************************************
> Achtung, wir sind umgezogen!
> Unsere neue Adresse:
> TIS GmbH
> Müller-Armack-Str. 8
> 46397 Bocholt
> ***********************************************
>
>
>
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
