The alternate accession code for an experiment is displayed on the search results page and experiment detail page. There's only one alternate accession code per experiment right now so the code is dependent on that fact. Also I put a function getUrlForCode in helpers.js but I can always move it if there's a better place to have that.
Types of changes
What types of changes does your code introduce?
Put an x in the boxes that apply
[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
Functional tests
Since this is dependent on the Experiment Detail endpoint having the alternate_accession_code field, I've merged that change into the backend but tested this change using the locally hosted API, which works for the experiments on there.
Checklist
Put an x in the boxes that apply.
[x] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)
[x] Any dependent changes have been merged and published in downstream modules
Issue Number
#871
Purpose/Implementation Notes
The alternate accession code for an experiment is displayed on the search results page and experiment detail page. There's only one alternate accession code per experiment right now so the code is dependent on that fact. Also I put a function
getUrlForCodeinhelpers.jsbut I can always move it if there's a better place to have that.Types of changes
What types of changes does your code introduce? Put an
xin the boxes that applyFunctional tests
Since this is dependent on the Experiment Detail endpoint having the
alternate_accession_codefield, I've merged that change into the backend but tested this change using the locally hosted API, which works for the experiments on there.Checklist
Put an
xin the boxes that apply.