DRYD-1506: Add published related links #51
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mikejritter
force-pushed
the
dryd-1506
branch
from
35e945a to
fd63c32
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this do?
Why are we doing this? (with JIRA link)
Jira: https://collectionspace.atlassian.net/browse/DRYD-1506
The
publishedRelatedLinkGroupListwas added to core and is now being added to profiles which can use it.How should this be tested? Do these changes have associated tests?
npm run devserver --back-end=https://herbarium.dev.collectionspace.orgReference Informationsection and see that the published linksDependencies for merging? Releasing to production?
I wasn't entirely sure of which templates to add this to for all profiles. It was added to default and photo here as they both have the reference section. The public template is disabled so it was skipped.
Has the application documentation been updated for these changes?
No
Did someone actually run this code to verify it works?
@mikejritter tested using herbarium.dev as a backend