|(3 intermediate revisions by 2 users not shown)|
Checker Framework = |+|
| || |
|−|A generic framework should be created which provides the foundation for other plugins to report errors. Right now we have the problems toolview but it is tightly coupled to the DUChain. This should be changed to use a separate item repository which stores the problems for a given path. The data stored would be: Path and range of where the issue is found, a short error message and optionally a long description. Furthermore, plugins might want to store additional info from which the problem could be fixed (compare to the 'add include path' or similar wizards we have already in the language framework). |+|
which . the to the of to from .
| || |
|−|This framework should then be used to integrate various tools. |+|
| || |
|−|* First of all the existing language plugins should show the problems they find there. |+|
|−|* The existing playground plugins for krazy and cppcheck integration should reuse that framework | |
|−|* any other linters could be integrated, such as jslint, pylint etc. pp. | |
|−|* runtime checkers could be integrated, such as valgrind's memcheck, ptrcheck, helgrind, drd, ... | |
| || |
|−|= SVN Plugin Rewrite = |+|
|−|The existing SVN plugin uses an outdated kdevsvncpp checkout internally which causes troubles, warnings and licensing issues. Port the plugin to either the C-API of svn or alternatively try to reuse code from current kdevsvn. |+|
Latest revision as of 09:08, 7 August 2017
SVN Plugin Rewrite
The existing SVN plugin uses an outdated kdevsvncpp checkout internally which causes troubles, warnings and licensing issues. Port the plugin to either the C-API of svn or alternatively try to reuse code from current kdevsvn.
Implement support for Language Server Protocol
Idea from Kevin.
This page was last edited on 7 August 2017, at 09:08. Content is available under Creative Commons License SA 4.0
unless otherwise noted.