Daniel Woste
Daniel Woste
Puhh, that's not so easy. The problem is, that an updated needs.json can have impact on so many pages and it is hard or maybe even impossible to figure out,...
@Chriner Sorry for the late response. Missed this ticket. It is not different for the needs itself. But there may be needtables and co. on other pages, which are based...
Also thought about this in the past. Another solution would be to allow custom names for columns in ``needtable`` and co.: ``` .. needtable:: :filter: status == "open" :columns: id,...
Have created #299 for the needtable column title feature.
The change will not be so easy, as a lot of code is working with `needs_extra_options`. So changing the allowed data types would affect a lot of code, which is...
Good point, the documentation and especially a check for this is missing. Thanks for reporting this. :+1:
It got documented. Thanks for the report.
Great idea :+1: Maybe we can make your approach even more generic to allow the definition of python code. Example: ``` .. needttable: :colums: id, title, code(len(incoming)), code(if outgoing "Yes"...
Interesting bug, can't imagine right now, why this is not working. Sure, Sphinx keeps all needs in its cached environment. But a changed file should recreate the related need and...
@Chriner that's a good hint. The need gets created, manipulated and stored during the first build. On the second build, the need gets not recreated (as the related file was...