SOSL find clause WITH USER_MODE or SYSTEM_MODE

[adangel]

Reposting the issue from google/summit-ast#53 here:

apex-parser doesn't support WITH USER_MODE and WITH SYSTEM_MODE when used in SOSL.

The Apex documentation is not clear, because:

• According to https://developer.salesforce.com/docs/atlas.en-us.248.0.apexcode.meta/apexcode/apex_classes_enforce_usermode.htm and https://developer.salesforce.com/docs/atlas.en-us.248.0.apexcode.meta/apexcode/apex_classes_with_security_enforced.htm it should be available for both SOQL and SOSL. The examples are all SOQL, though...

  You can indicate the mode of the operation by using WITH USER_MODE or WITH SYSTEM_MODE in your SOQL or SOSL query.

• The SOSL documentation doesn't list this: https://developer.salesforce.com/docs/atlas.en-us.soql_sosl.meta/soql_sosl/sforce_api_calls_sosl_syntax.htm

Is the following code valid Apex code?

public inherited sharing class soqlExample {

  public static String example(){
    String SecondarySearchList = 'test';

    List<List<SObject>> accountList = [
      FIND :SecondarySearchList
      IN NAME FIELDS
      RETURNING Account(Id, Account.Name WHERE ID = '' LIMIT 100)
      WITH USER_MODE
    ];
  }
}

If yes, then someone needs to update the SOSL documentation and we probably need to enhance the parser:

apex-parser/antlr/ApexParser.g4

Lines 826 to 838 in 2f9160c

	soslClauses
	: (IN searchGroup)?
	(RETURNING fieldSpecList)?
	(WITH DIVISION ASSIGN StringLiteral)?
	(WITH DATA CATEGORY filteringExpression)?
	(WITH SNIPPET (LPAREN TARGET_LENGTH ASSIGN IntegerLiteral RPAREN)? )?
	(WITH NETWORK IN LPAREN networkList RPAREN)?
	(WITH NETWORK ASSIGN StringLiteral)?
	(WITH PRICEBOOKID ASSIGN StringLiteral)?
	(WITH METADATA ASSIGN StringLiteral)?
	limitClause?
	(UPDATE updateList)?
	;

If no, then someone just needs to clarify the Apex documentation and remove the SOSL reference.

[kjonescertinia]

That code can be deployed so think this is an issue that needs fixing. Thanks for highlighting this, will try and get a fix done this week.

[pwrightcertinia]

Fix now available in v4.1.0 release, thanks for the report!