Skip to content

Document excluded Salesforce namespaces #72

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.

Sign up for GitHub

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

Merged
kjonescertinia merged 1 commit into from
Jun 9, 2026
Merged

Document excluded Salesforce namespaces #72

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,25 @@ These stub declarations help support static analysis of Apex code in [apex-ls](h

The library is versioned to reflect Salesforce API numbers, so currently v65.X.X matches the Salesforce Winter '26 API.

## Coverage Scope

This project covers Salesforce platform types that are useful for Apex static analysis, especially for the expected
usage of [apex-ls](https://github.com/apex-dev-tools/apex-ls). It does not aim to mirror every industry or product
namespace that Salesforce exposes.

Some Salesforce namespaces are intentionally excluded when they are product-specific and have no expected relevance to
the current tooling use cases. Known exclusions include:

- `hlthcrbilling`
- `runtime_industries_insurance`
- `IssueCreditMemo`
- `RulesAppln`
- `renew_assets_summary`

The Revenue/Billing exclusions do not mean every commerce, quote, payment, or revenue-related type is out of scope.
Existing covered namespaces such as `CommercePayments`, `CommerceOrders`, `PlaceQuote`, `RevSalesTrxn`, `RevSignaling`,
and related `ConnectApi` commerce types remain supported where they are already useful to the analyzer.

## Installation

To use the jar in a maven project add the following to your pom.xml
Expand Down
Loading