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

Rename variorum_get_node_frequency_json --> variorum_get_frequency_json #502

Merged
merged 1 commit into from
Jan 29, 2024

Conversation

slabasan
Copy link
Collaborator

Description

Rename top-level API variorum_get_node_frequency_json to variorum_get_frequency_json

Fixes #498

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature/architecture support (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update
  • Build/CI update
  • Internal cleanup

Checklist:

  • I have run ./scripts/check-code-format.sh and confirm my code code follows the style guidelines of variorum
  • I have added comments in my code
  • My changes generate no new warnings (build with -DENABLE_WARNINGS=ON)
  • New and existing unit tests pass with my changes

@slabasan slabasan added status-ready-for-review Formatted, and tested on multiple systems. type-internal-cleanup area-internal labels Jan 29, 2024
@slabasan slabasan added this to the Production: v0.8.0 Release milestone Jan 29, 2024
@slabasan slabasan force-pushed the rename-freq-json-api branch from 07e2195 to 7509328 Compare January 29, 2024 22:57
@slabasan slabasan force-pushed the rename-freq-json-api branch from 7509328 to ca75b7a Compare January 29, 2024 23:03
@slabasan slabasan merged commit e81a6c4 into dev Jan 29, 2024
15 of 16 checks passed
@slabasan slabasan deleted the rename-freq-json-api branch February 16, 2024 18:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Rename get frequency API
1 participant