Skip to content

only include constraint in payload when explicitly set#198

Closed
edx4900 wants to merge 1 commit intodynotx:mainfrom
edx4900:fix-update-entity-schema
Closed

only include constraint in payload when explicitly set#198
edx4900 wants to merge 1 commit intodynotx:mainfrom
edx4900:fix-update-entity-schema

Conversation

@edx4900
Copy link
Copy Markdown
Contributor

@edx4900 edx4900 commented Mar 17, 2026

Motivation

When UpdateEntitySchema was called to update only non-constraint properties, this would resend the existing constraint. Benchling interpreted this as attempting to add an additional constraint and would reject it as a duplicate add.

Fix

This fix excludes the constraint from the update payload when constraint_fields isn't part of the requested changes

@nirmit-damania-dyno
Copy link
Copy Markdown
Collaborator

Hey! Good catch. I went ahead and made a separate branch with my implementation of the fix, which fixes the root of issue. Let me know if this makes sense and how it looks to you and we can merge it in!

#201

@edx4900 edx4900 closed this Mar 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants