Skip to content

Expand Salesforce metadata and frontend indexing#11

Open
krzysztofwojt wants to merge 1 commit into
DFKHelper:mainfrom
krzysztofwojt:feat/salesforce-indexing-expansion
Open

Expand Salesforce metadata and frontend indexing#11
krzysztofwojt wants to merge 1 commit into
DFKHelper:mainfrom
krzysztofwojt:feat/salesforce-indexing-expansion

Conversation

@krzysztofwojt

Copy link
Copy Markdown
Contributor

Summary

  • index every Salesforce *-meta.xml with stable fallback symbols
  • add detailed symbols and selected references for Flow, object metadata, Custom Labels, LWC, Aura, and Visualforce
  • add Salesforce-aware LWC imports, templates, targets, and properties plus dedicated salesforce_markup
  • cover the real default worker path and the built bundle with a Salesforce DX fixture

Why

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 typecheck
  • npm run lint
  • npm run test:guards (13/13)
  • targeted Salesforce, parser, worker, and embeddings tests (55/55)
  • built dist/token-goat.mjs Salesforce smoke tests (2/2)
  • synthetic scale test: 2,700 files, 5,500 symbols, 600 refs, 0 duplicate symbols/refs, 0 unknown *-meta.xml

Notes

  • no database schema migration
  • long-tail metadata gets a stable top-level symbol; deeper extraction is limited to high-value types

@krzysztofwojt

Copy link
Copy Markdown
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 ;)

@krzysztofwojt krzysztofwojt marked this pull request as ready for review July 10, 2026 09:46
@krzysztofwojt

Copy link
Copy Markdown
Contributor Author

Okay, ready.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant