Add chokidar-as-cli example and implement Lua library functions#490
Open
gesslar wants to merge 1 commit into02-21-refactor_update_example_plugins_and_hooks_for_formatter_renamefrom
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
This was referenced Feb 22, 2026
Owner
Author
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
5c5aa12 to
66479dc
Compare
66479dc to
8139fd6
Compare
1d73c81 to
3835025
Compare
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
3835025 to
fba67a7
Compare
8139fd6 to
f8266c4
Compare
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
Adds a curated set of 4 representative source files per parser type as test fixtures for validating the Lua and C parsers:
examples/source/lua/—string.lua,date.lua,table.lua,func.lua(updated from meta definitions to implementations)examples/source/lua-library-source/— same 4 files as reference library variants (new meta definitions)examples/chokidar-as-cli/src/—string.c,function.c,data.c,numbers.c(new C function declarations)examples/source/lpc/data.c— minor annotation update adding@return {void}todata_writeThe same 4 filenames are used across the Lua directories to ensure reproducibility when testing the same parser logic under different source contexts (standalone vs. library source). Files were chosen to cover a range of documentation patterns: simple utilities, date/time functions with rich annotations, collection utilities, and functional patterns.
Test plan
examples/source/lua/and verify Lua parser produces outputexamples/source/lua-library-source/and confirm same parser logic appliesexamples/chokidar-as-cli/src/and verify C parser produces output