Makes r_params backwards compatible for UVPSpec #219
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.
Any new parameter added to our file formats (including
PSpecContainer
andUVPSpec
) must have a catch in theirread()
functions to catch for the case that the parameter is not defined.This wasn't caught in our normal review process b/c we don't store static
UVPSpec
objects in our testing directly, and create them on-the-fly in our testing suite. This was done b/c our file format and its API was actively changing, but now that things have settled down I think its a good idea to make one simple staticUVPSpec
file in our data directory to specifically catch these backwards compatibility errors. Therefore, an exampleuvp
object is added to the data dir and a simpleread()
test is added totest_uvpspec
.addresses #220