feat: add camelCase API aliases - #69
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add idiomatic camelCase aliases for TypeScript consumers while preserving the snake_case parity API, update Vitest dependencies to a vulnerability-free release, and prepare package version
0.9.0-dev.2.Why
TypeScript consumers can use camelCase methods and grammar helpers without changing the Python-compatible API or conformance contract.
Scope checklist
npm test)Notes
exportJson,importJson,applyDirectivedecomposeDirective,getDirectiveMetadataValidation details:
npm test: passed (266/266)npm run build: passednpm audit: 0 vulnerabilitiesnpm pack --dry-run: passed