Remote action methods in page cannot complete/find usage methods in page controllers superclass

In our project, we have pages that within a section of javascript make RemoteAction calls to a method that is available on the page controllers superclass. This enables us to create ‘base’ controllers for code reuse. However these methods are never linked/findable/completable despite the code being deployable and working fine. This leads to the danger of refactoring of base methods breaking our pages.

For example

Given the following

public virtual with sharing class Base_Controller {

    @RemoteAction
    public static String getMeSomethingUsingBase() {
    }
}

public with sharing class New_Page_Controller extends Base_Controller {

    @RemoteAction
    public static String getMeSomethingUsingNewPage() {
    }
}

<apex:page controller="New_Page_Controller">
    <html>
        <head>
            <script defer="defer">
                window.addEventListener("load", function() {

                    const findable = new some.packaged.js.method({
                        id: 'findable',
                        methods: {
                            get: {
                                method: '{!$RemoteAction.New_Page_Controller.getMeSomethingUsingNewPage}'
                            }
                        }
                    });

                    const not-findable = new some.packaged.js.method({
                        id: 'not-findable',
                        methods: {
                            get: {
                                method: '{!$RemoteAction.New_Page_Controller.getMeSomethingUsingBase}'
                            }
                        }
                    });
            </script>
        </head>

        <body></body>

    </html>
</apex:page>

In this example the first RemoteAction allows for completion whilst typing, is findable and refactorable as it references the page controllers own method.

The second RemoteAction does not complete, not is it findable or refactorable as it references the page controllers superclass method.

Comments (9)