-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Add functions for parameter validity check and parameter transformation #308
Labels
🚀 feature
New feature or request
Comments
chrwm
added a commit
that referenced
this issue
Jul 25, 2022
1 task
chrwm
added a commit
that referenced
this issue
Jul 25, 2022
deniztepe
added a commit
that referenced
this issue
Aug 19, 2022
deniztepe
added a commit
that referenced
this issue
Aug 19, 2022
The parameter 'technology' is replaced with 'data' wherever it means more than only technologies. It requires a thorough scan of scripts for a consistent refactoring. The documentation must be adapted as well.
deniztepe
added a commit
that referenced
this issue
Aug 22, 2022
*api_data_types and api_location_types default now to all possible selections. * transform function returns lists required from lower functions -> lower functions must handle only lists -> no parsing etc.
5 tasks
deniztepe
added a commit
that referenced
this issue
Aug 24, 2022
* Technology is renamed to data where necessary * In docstring, a table for possible data values is added
Closed with #337 |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Create new set of functions or edit existing functions that can handle the parameter harmonisation adressed in #252:
validate_parameter_tables(method, data)
checks if parameter values and chosen method ("API" or "bulk") work togethertransform_parameter
creates new parameters that are needed for the download depending on the user input (such as api_location_types if "location" indata
andmethod
="API")The text was updated successfully, but these errors were encountered: