-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
need_count throws warning with sphinx-needs 1.0.1 #672
Comments
Hi @twodrops, I tried In your example above, is the extra option If so, I need more info to analyze. Could you please provide a minimal example that can reproduce the warning? |
@haiyangToAI That's right Thanks for checking this out. |
Hi @twodrops, After analyzing the documents you mentioned, I found the reason why those warnings appear. First of all, it might seems those warnings are caused by The warnings are legit. From the warning example above, it suggests that the filter string This made me wonder why extra option
I will fix it soon. |
@haiyangToAI Thanks for analysing this and finding out the root cause. Also thanks for creating the issue. |
I close this issue as it is no problem for Sphinx-Needs and gets solved here: useblocks/sphinx-test-reports#41 |
If a filter with an own
needs_extra_option
is used withinneed_count
, a warning a thrown. The output is however created correctly. This was not the cases with 0.7.9.Example:
Throws
The first filter with
type
throws no warning.The text was updated successfully, but these errors were encountered: