You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using need_extract to show a "different" view on the need creates an entry in html with same id as the original one.
This leads to "WARNING: Anchor defined twice" in generation of pdf from html with sphinx-simplepdf.
Could there be an option to "prefix" the ID generated in html output, so that the id is generated from the prefix and the "original" id from the requirement? Or how could this be solved.
Or is there an other way to show the content of a need? Dynamic functions are not usefull, cause if they contain rst formats they are not rendered correctly.
What should be achieved
The content of a need should be reused in documentation for SOT principle. This should be achieved by getting the content of the need (rendered, dynamic functions like with needextract)
What does not help
Dynamic functions could return the content, but as text only without any rst parsing or other resolved stuff. Therefore the output is not fully usable.
What could be used
needextract seems to work, but generates several outputs in the document with the same link/reference id. The content is rendered good and could be styled/layouted to integrate into the document text.
The text was updated successfully, but these errors were encountered:
Using need_extract to show a "different" view on the need creates an entry in html with same id as the original one.
This leads to "WARNING: Anchor defined twice" in generation of pdf from html with sphinx-simplepdf.
Could there be an option to "prefix" the ID generated in html output, so that the id is generated from the prefix and the "original" id from the requirement? Or how could this be solved.
Or is there an other way to show the content of a need? Dynamic functions are not usefull, cause if they contain rst formats they are not rendered correctly.
What should be achieved
The content of a need should be reused in documentation for SOT principle. This should be achieved by getting the content of the need (rendered, dynamic functions like with
needextract
)What does not help
Dynamic functions could return the content, but as text only without any rst parsing or other resolved stuff. Therefore the output is not fully usable.
What could be used
needextract
seems to work, but generates several outputs in the document with the same link/reference id. The content is rendered good and could be styled/layouted to integrate into the document text.The text was updated successfully, but these errors were encountered: