Skip to content

Enhance preset creation to ensure unique entries for identical component codes#9553

Open
Davron129 wants to merge 6 commits intomasterfrom
9489-nucleotide-presets-creating-preset-with-the-same-component-codes-replaces-properties-of-the-existing-preset
Open

Enhance preset creation to ensure unique entries for identical component codes#9553
Davron129 wants to merge 6 commits intomasterfrom
9489-nucleotide-presets-creating-preset-with-the-same-component-codes-replaces-properties-of-the-existing-preset

Conversation

@Davron129
Copy link
Copy Markdown
Collaborator

@Davron129 Davron129 commented Mar 26, 2026

How the feature works? / How did you fix the issue?

Commented check for hidden props for future use and added check for Name to monomer comparison function

Check list

  • unit-tests written
  • e2e-tests written
  • documentation updated
  • PR name follows the pattern #1234 – issue name
  • branch name doesn't contain '#'
  • PR is linked with the issue
  • base branch (master or release/xx) is correct
  • task status changed to "Code review"
  • reviewers are notified about the pull request

Davron129 and others added 5 commits April 2, 2026 05:43
…-presets-creating-preset-with-the-same-component-codes-replaces-properties-of-the-existing-preset
…th-the-same-component-codes-replaces-properties-of-the-existing-preset
…-presets-creating-preset-with-the-same-component-codes-replaces-properties-of-the-existing-preset
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Nucleotide presets: Creating preset with the same component codes replaces properties of the existing preset

2 participants