Skip to content

fix: add missing support for primaryKeyConstraintName property in EntitySchema#9336

Merged
AlexMesser merged 1 commit intomasterfrom
entity-schema-ccn
Aug 30, 2022
Merged

fix: add missing support for primaryKeyConstraintName property in EntitySchema#9336
AlexMesser merged 1 commit intomasterfrom
entity-schema-ccn

Conversation

@AlexMesser
Copy link
Copy Markdown
Collaborator

@AlexMesser AlexMesser commented Aug 30, 2022

Description of change

  • adds missing support for primaryKeyConstraintName property in EntitySchema definition
  • adds tests for another custom constraint names in EntitySchema definition

Fixes #9309

Pull-Request Checklist

  • Code is up-to-date with the master branch
  • npm run format to apply prettier formatting
  • npm run test passes with this change
  • This pull request links relevant issues as Fixes #0000
  • There are new or updated unit tests validating the change
  • Documentation has been updated to reflect this change
  • The new commits follow conventions explained in CONTRIBUTING.md

@AlexMesser
added support for custom PK constraint name in entity schema definition;
5cc60c5 
added tests with custom constraint names for entity schemas;
@AlexMesser AlexMesser merged commit cc63961 into master Aug 30, 2022
@AlexMesser AlexMesser deleted the entity-schema-ccn branch August 30, 2022 16:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Support PrimaryKeyConstraintName for EntitySchema

1 participant

@AlexMesser