-
Notifications
You must be signed in to change notification settings - Fork 243
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
feat(cxx_indexer): use default corpus for meta, builtin nodes #5008
Conversation
this should be a no-op unless --use_compilation_corpus_as_default is enabled, in which case these nodes will be assigned the compilation unit's corpus. KytheGraphObserver's constructor emits nodes for builtins and meta nodes, so setting the default corpus later means it won't apply to these nodes. The constructor has been modified to accept a default_corpus parameter, which is set to the compilation unit's corpus when --use_compilation_corpus_as_default is enabled. A new test was added that reads the indexer output for a test example and checks that each vname has a non-empty corpus.
I'm having trouble getting Any tips on getting that working? |
Use (Or match the VName path and use vnames.json to map it appropriately when extracted) |
Thanks! I tried that and realized the issue was that I needed to use |
This should be a no-op unless --use_compilation_corpus_as_default is
enabled, in which case these nodes will be assigned the compilation
unit's corpus.
KytheGraphObserver's constructor emits nodes for builtins and meta
nodes, so setting the default corpus later means it won't apply to these
nodes. The constructor has been modified to accept a default_corpus
parameter, which is set to the compilation unit's corpus when
--use_compilation_corpus_as_default is enabled.
A new test was added that reads the indexer output for a test example
and checks that each vname has a non-empty corpus.