BI-2019 - Pedigree Viewer Not Rendering #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.
Description
Jira Story
This PR completes the work that was done in this commit to type
additionalInfo
fields asJsonObject
.The brapi-java-client was trying to parse
additionalInfo
onBrAPIPedigreeNode
objects, which can have nested objects, as a strict Map<String, String>, which resulted in the errorExpected a string but was BEGIN_OBJECT
.Testing
Step 0. [OPTIONAL] Reproduce the bug by running bi-web and bi-api, uploading germplasm to a BJTS program and trying to use the pedigree viewer.
git clone https://github.com/Breeding-Insight/brapi
.git checkout bug/BI-2019
.clean install -D maven.test.skip=true
(with the root directory of the repo ("brapi") as the working directory).brapi-java-client
dependency and replace it with the following, substituting the absolute path to the brapi repo on your local machine for {PATH_TO_BRAPI_REPO}.These general steps have been documented on Confluence, https://breedinginsight.atlassian.net/wiki/x/AQC6dg, please add anything you learn in the process of testing there.