-
Notifications
You must be signed in to change notification settings - Fork 5
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
Processing of subcategories in FDC reporting #11
Comments
Two issues here:
At the very least we should make it clear that fdc.py is not recursive. |
There is category_flattening which was created for this issue but is still Caroline 2014-08-13 0:30 GMT+02:00 Jean-Frédéric notifications@github.com:
|
Agreed ; if we decide to support this use case I would rather try to connect to @dschwen FastCCI, not implement it ourselves. |
fdc.py is not recursive and should not be. It's a bad tracking practrice not to have categories the way I decide! :) |
I agree with you @PierreSelim. I think we should
|
WON'T FIX :-) |
Hum, guys, I totally disagree with you on this and I would really have Caroline 2014-08-26 8:28 GMT+02:00 Pierre-Selim notifications@github.com:
|
@Krho please subscribe to your issue and answer :) It's reopen. |
I'd be happy to help (by adding all necessary APIs to FastCCI). |
As a chapter, I want wm_metrics to report on all the files in subcategories of the given category to analyse, in order to get a complete report.
(This use case was submitted by the Austrian chapter, who uses subcategories and does not have a hold-all category)
The text was updated successfully, but these errors were encountered: