Nirmal Sasidharan
Nirmal Sasidharan
I also feel both options are good. I am wondering if the feature in `needtable` could result in some "confusions" because of the duplication within `needtable`. For example, someone starts...
@danwos @StephanKuempel I find `needs_option_titles = {"new_option": "Another Name"}` not the most ideal, but as you both mentioned, the most low impact solution for now.
@arwedus This is a known issue and needs fix within breathe. See https://github.com/useblocks/sphinxcontrib-needs/issues/231
I vote for this. It would be great to have a type-specific need definition, which is also self-contained.
+1 for this
@danwos @haiyangToAI I would like to know a bit more on this snippet feature. The current snippet feature is useful only to know which need-types (directives) are available. The snippet...
Thanks for the clarification @danwos. This means that the need-definitions and `needs_ide_snippets ` needs to be kept in sync manually. I find this better than keeping it in sync with...
@danwos Yes, the second part. The imported needs with `needimport` shall not be exported. I guess this can be done by using "tags" with `needimport` and a filter expression in...
Slightly offtopic, but good point. > But this counter is not based on specific options or the content. Maybe a feature request to extend this mechanism would be helpful. Separate...
ah, sorry I completely forgot about https://sphinxcontrib-needs.readthedocs.io/en/latest/configuration.html#needs-css Therefore it makes sense to leave it to the user to customize it to match the theme used. We could close this. Thanks...