Expand Salesforce metadata and frontend indexing#11
Open
krzysztofwojt wants to merge 1 commit into
Open
Conversation
Contributor
Author
|
Hi @Zelys-DFKH , please give me some time to manually review my changes here, I'll change the status to ready to review once I'm sure it's really ready ;) |
Contributor
Author
|
Okay, ready. |
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
*-meta.xmlwith stable fallback symbolssalesforce_markupWhy
This builds on the Apex and metadata indexing merged in #9. The original adapter covered core Apex and selected XML metadata, but frontend bundles and much of Salesforce source-format metadata remained unknown or only generically searchable.
Validation
npm run typechecknpm run lintnpm run test:guards(13/13)dist/token-goat.mjsSalesforce smoke tests (2/2)*-meta.xmlNotes