It would be great if Codelinks could extract source-code related information from the tagged class/function and add it to the needed, so that the needs has information about:
- Function/class name
- Used function parameters
- function/class docstring (may be later used as need content)
- source code itself
Maybe the data extraction should be separate from need-assignment, to have a list of all scanned/parsed classes/functions.
This would allow to report functions without any linked Sphinx-Needs element.
It would be great if Codelinks could extract source-code related information from the tagged class/function and add it to the needed, so that the needs has information about:
Maybe the data extraction should be separate from need-assignment, to have a list of all scanned/parsed classes/functions.
This would allow to report functions without any linked Sphinx-Needs element.