feat(stdlib)!: Add required usage method to all functions#1608
Merged
thomasqueirozb merged 10 commits intomainfrom Jan 15, 2026
Merged
feat(stdlib)!: Add required usage method to all functions#1608thomasqueirozb merged 10 commits intomainfrom
thomasqueirozb merged 10 commits intomainfrom
Conversation
bfung
approved these changes
Jan 15, 2026
bfung
left a comment
bfung
left a comment
There was a problem hiding this comment.
Approving for "it works" technically, not going to scrutinize all the content as that can be improved over time.
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
2 participants
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
Added
usage()method implementations to all VRL stdlib functions. Theusage()method is now required on theFunctiontrait.The descriptions were copied over from the Vector repo from
website/cue/reference/remap/functions/*.cuePart of the automatic documentation generation RFC (#280)
Change Type
Is this a breaking change?
How did you test this PR?
Verified all functions compile with
cargo check.Does this PR include user facing changes?
References
NA