-
-
Notifications
You must be signed in to change notification settings - Fork 52
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
Summarize attributes into a request object #8
Comments
Dear Daniel, while working on the Am I right to assume that this already bundles all request attributes into this very class/object with the intention outlined in your original post? However, after scanning the code base further, I found Did I miss something here or have you just been able to lay the groundwork for upcoming features where With kind regards, |
Dear Benjamin, now I am seeing your improvements on the With kind regards, [1] https://github.com/gutzbenj/python_dwd/commits/Feature/21/stationdata-request-definition |
Dear @amotl , it took me quite a while to outline the functioning of DWDStationRequest, but you're absolutely right, the next PR from my side will include a method to source all the data as defined by the request. |
Hi Benjamin,
Thanks, I am absolutely looking forward to that. Right now, my basic As far as I can see, #52 can be abandoned then as Keep up the great work and with kind regards, |
It shouldn't take more then a few days - I usually want to rely on @meteoDaniel 's feedback/review as a maintainer for any PR. |
Several times var(parameter) res (time_resolution) and per(period_type) are parsed to functions. It would make sense to create a dataclass holding these attributes. Within this way we can guarantee all required information are correctly parsed to the different functions.
The text was updated successfully, but these errors were encountered: