ANW-2270 Fix the accession linker prelinker bug on Archival Object forms#3471
Conversation
|
@jdshaw great find! Could you add a feature spec to this? |
|
@thimios Will do on the feature spec. Might take a minute to get up to speed on the current state of those, but hopefully next week. |
|
I think https://github.com/archivesspace/archivesspace/blob/master/frontend/app/views/component_links/_component_linker.html.erb may need a similar fix, though I could not replicate a similar behavior when adding archival objects to an accession. That makes me wonder if there's something 'special' about the archival object CRUD. |
|
Feature spec added. |
|
@jdshaw @thimios I looked at all the frontend linkers, including the "component linker" mentioned above, and did not find any other issues, apart from the (minor) duplicate alerts bug on the Classifications subform which has been fixed via #3474. Once the spec herein is finalized this looks good to merge from my end. |
thimios
left a comment
There was a problem hiding this comment.
Some comments on the spec, the rest looks good!
|
Changes as suggested by @thimios in place. |
The review has been incorporated.
As described in ANW-2270, accession links will be removed on resave if they number more than 5 (and are thus initially hidden)
Description
Updates the linker template for accession links to provide
prelinkerclassed input fields and updates the id for each linker form. Adds additional feature spec for archival object accession links.Related JIRA Ticket or GitHub Issue
ANW-2270
How Has This Been Tested?
Local Testing under 4.0.
Screenshots (if appropriate):
Types of changes
Checklist: