-
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
timeframe_n_last_days is not supported yet #19
Comments
I didn't manage to finish this so far because I wasn't sure yet how to expose this to the CLI. Similarly, I wasn't sure how the config file would ideally look like. I.e. the simple approach: [timeframe] or more like this: [timeframe] [timeframe:n_last_days] The latter is similar to how plugins are currently expressed in the config and seems more extensible to me. But it could also be overhead since it's dubious if other timeframes (than those already present) will be necessary. So I would like to get your opinion on that and simply implement the missing bits in rapport/cli.py. |
I prefer the latter unless it's significantly more complex to implement. I think a timeframe allowing an arbitrary date range is worth while, and in that instance you would want
|
And this would simply map to the Timeframe base class. I'll do it this way then |
Now I see:
but no corresponding entry in |
Also the sample |
No parameters are ever currently passed to the constructor of a
Timeframe
subclass. In particular, the config settingtimeframe_n_last_days
is totally ignored. I'm not sure why it was ever included inrapport.conf
?The text was updated successfully, but these errors were encountered: