Remove _batch
from archive add() parameter names
#422
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Removes the
_batch
suffix from parameter names for add(), e.g.,solution_batch
just becomessolution
. This change helps to make way for #421, where we support custom fields. With custom fields, it makes sense to just have the field name in the argument, e.g.,myfield
, rather thanmyfield_batch
. Thus, this PR makes the current argument names consistent with this usage.Furthermore, the names with
_batch
are rather verbose, as it is usually clear from context whether the data is batch or singular (i.e., our methods mostly take in batch data, and when they need single data, they are named with the_single
suffix, e.g.,add_single
).This change is not as likely to affect users, since most only deal with the scheduler and do not call the archive directly; furthermore, most who do use add will only pass in their arguments positionally -- our schedulers currently use positional arguments.
TODO
Questions
Status
CONTRIBUTING.md
yapf
pytest
pylint
HISTORY.md