skill: baml describe shows camelCase names but invocation uses snak…#3
Draft
ATX24 wants to merge 1 commit into
Draft
skill: baml describe shows camelCase names but invocation uses snak…#3ATX24 wants to merge 1 commit into
ATX24 wants to merge 1 commit into
Conversation
Builder fix for issue #25
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
1 participant
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.
Auto-drafted by
baml-bench-builderfrom builder issue #25.Issue
baml describe shows camelCase names but invocation uses snake_case
The baml:core skill documents stdlib methods in snake_case (char_at, index_of, replace_all), which is the correct invocation form under baml-lang. However, baml describe String surfaces underlying source names in camelCase (charAt, indexOf, replaceAll), causing agents who use describe for discovery to write camelCase calls. Cold-start agents using baml-py v0.222.0 additionally found that camelCase is the actual invocation form for that CLI, making the correct spelling version-dependent. The skill should warn that describe output reflects internal source spelling, clarify which runtime version is expected, and reaffirm that snake_case is the correct form for baml-lang.
Builder summary
Builder fix for issue #25
Evidence
5657585960This is a draft PR generated from deduplicated agent reports. Review before merging.