Skip to content

feat!: change extension names to use camel case convention - #245

Merged
korikuzma merged 1 commit into
stagingfrom
issue-243
Aug 12, 2026
Merged

korikuzma merged 1 commit into
stagingfrom
issue-243

Conversation

@korikuzma

Copy link
Copy Markdown
Collaborator

close #243

  • variant_types -> variantTypes
  • CIViC Molecular Profile Score -> molecularProfileScore
  • CIViC representative coordinate -> representativeVariantCoordinates
  • is_approved_vcep -> isApprovedVcep
  • clinvar_accession -> clinvarAccession

@korikuzma korikuzma self-assigned this Jul 15, 2026
@korikuzma korikuzma linked an issue Aug 3, 2026 that may be closed by this pull request
@korikuzma
korikuzma changed the base branch from issue-209 to issue-209-gks August 3, 2026 17:30
@korikuzma
korikuzma force-pushed the issue-243 branch 2 times, most recently from 7e601ef to c682735 Compare August 5, 2026 12:59
@korikuzma
korikuzma marked this pull request as ready for review August 5, 2026 13:04
Base automatically changed from issue-209-gks to staging August 10, 2026 13:34
@korikuzma

Copy link
Copy Markdown
Collaborator Author

@susannasiebert or @acoffman This is ready for review!

@susannasiebert susannasiebert left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

+1

@korikuzma
korikuzma merged commit b9b019c into staging Aug 12, 2026
4 checks passed
@korikuzma
korikuzma deleted the issue-243 branch September 10, 2026 11:02
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.

GKS: Extension names should use camel case naming convention

2 participants