Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Account for Collection Prefs when cloning/carry forwarding #4160

Merged
merged 5 commits into from Nov 13, 2023

Conversation

melton-jason
Copy link
Contributor

Fixes #3278

TO TEST:

  • Ensure the CO_CREATE_PREP_<COLLECTION> preference is defined in Remote Preferences

    • Replace <COLLECTION> with the id of the collection you are testing this in
  • Clone and Carry Forward a CollectionObject which has existing preparations.

  • Clone and Carry Forward a CollectionObject which does not have preparations

  • Test the other "collection preferences" related to automatic resource creation/initialization which can be defined in Remote Preferences:

    • CO_CREATE_COA_ (Collection Object Attribute)
    • CO_CREATE_DET_ (Determination)

@melton-jason melton-jason requested review from a team October 26, 2023 11:46
@melton-jason melton-jason marked this pull request as ready for review October 26, 2023 11:47
@melton-jason melton-jason requested a review from a team November 6, 2023 17:44
@CarolineDenis CarolineDenis added this to the 7.9.2 milestone Nov 6, 2023
@melton-jason melton-jason requested a review from a team November 8, 2023 18:17
Copy link
Contributor

@pashiav pashiav left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tested for both the Clone and Carry Forward features and they both do what is expected of them! No incorrect duplicates. Adding new determinations also works. Looks good!
Collection object with No Preparations:
issue-3278-no prep
Collection object with Existing Preparations:
issue-3278-prep

Added lines in remote pref:
Screen Shot 2023-11-09 at 10 23 08 AM

@melton-jason melton-jason merged commit 3430162 into production Nov 13, 2023
9 checks passed
@melton-jason melton-jason deleted the issue-3278 branch November 13, 2023 18:06
@specifysoftware
Copy link

This pull request has been mentioned on Specify Community Forum. There might be relevant details there:

https://discourse.specifysoftware.org/t/specify-7-9-2-release-announcement/1452/1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

Cloning incorrectly duplicates preparations
5 participants