RFC: Add opinion on @future methods

[YodaDaCoda]

@future methods are great, but sometimes you want to call the method synchronously. Propose a convention whereby all future methods do nothing more than call another non-future method. Naming convention for future/non-future method pairs TBC.

e.g.

BAD

@future
public static void myMethod(Account myAccount) {
    // do a whole bunch of things with myAccount
}

GOOD

@future
public static void myMethod_future(Account myAccount) {
    myMethod(myAccount);
}

public static void myMethod(Account myAccount) {
    // do a whole bunch of things with myAccount
}

[YodaDaCoda]

Personally, I like myMethod/myMethod_future but PMD will complain unless we adjust the ruleset.

[ehsankorhani]

GOOD

@future
public static void myMethodAsync(List<ID> recordIds) {
    // Query the sObject with the incoming parameter.
    myMethod(myAccount);
}

public static void myMethod(Account myAccount) {
    // do a whole bunch of things with myAccount
}