Returning Data to LWC: Wrapper Classes and DTOs

@AuraEnabled
public static List<Account> getAccounts() {
    return [SELECT Id, Name, Industry FROM Account];
}

For a component that just needs to display real Account fields directly, returning the queried sObject List is simple and works fine — exactly like every SOQL example since Module 20.

public class AccountSummary {
    @AuraEnabled public String name;
    @AuraEnabled public Integer openOpportunityCount;
    @AuraEnabled public Decimal totalWonRevenue;
}

@AuraEnabled
public static List<AccountSummary> getAccountSummaries() {
    List<AccountSummary> summaries = new List<AccountSummary>();

    for (Account acc : [SELECT Id, Name, Total_Won_Revenue__c, (SELECT Id FROM Opportunities WHERE IsClosed = false) FROM Account]) {
        AccountSummary summary = new AccountSummary();
        summary.name = acc.Name;
        summary.openOpportunityCount = acc.Opportunities.size();
        summary.totalWonRevenue = acc.Total_Won_Revenue__c;
        summaries.add(summary);
    }

    return summaries;
}

This is Module 16's wrapper-class pattern, applied at the LWC boundary: AccountSummary combines a real field (Name), a computed value (openOpportunityCount, from the child-relationship subquery, Module 20), and a rollup (Module 26) — a shape no single query alone could return directly, tailored to exactly what a dashboard component needs to display.

Notice @AuraEnabled appears on the fields of AccountSummary, not just the method — each field the UI needs to read must be individually exposed too, the same annotation-based exposure principle from Lesson 2, now applied one level deeper.