Arwed S.

> > ... it's simply unnecessary to store parts of the needs that do not add information > > I can't entirely agree in all cases, but to be backward-compatible...

@danwos: I'd argue that adding an option to a file that was not in before should not break any reasonably well implemented scripts. You just released a sphinx-needs 2.0 and...

good idea to make this a new ticket. I'm in favor of releasing sphinx-needs 1.4 this week over waiting until next week just to add this feature (if that's the...

Hi @danwos , I like the proposal. Please make "path" accept both absolute and relative paths. Just one open point: > > ⚠️ The data of `needs_importable_data` is not available...

@chrisjsewell : The way of importing is conceptually different. - needs_external_needs: Works like sphinx.ext.intersphinx, lets you link to needs defined in another sphinx project. You need another sphinx project. -...

@chrisjsewell : I have given you my perspective as a user of sphinx-needs. With needimport, I'm placing needs in my project, i.e. they appear as original "document nodes". with needs_external_needs,...

@AWhetter : Could you please review this PR? I don't understand why the test is failing for Py3.12, maybe you have an idea

The issue is not only related to Markdown. I have created for you an example that shows the same behavior in .h files using normal Doxygen @image tag. The example...

I have to correct myself: There is a warning generated (alternative 1): ~/doxygen-example/component2/doc/component2.md:9: warning: image file name img/structure.png is ambiguous. Possible candidates: ~/doxygen-example/component1/doc/img/structure.png ~/doxygen-example/component2/doc/img/structure.png Questions is whether you'd want to...

Hi @chrisjsewell , first of all thanks for tackling this topic, even before I had conducted the performance measurement :-) > Note, in #1148 there was discussion of "centralised, pre-caching",...