enh: interface for entrypoints

[gillyspy]

I do something like this:

in local types

import { EntryPoints } from 'N/types';

interface clientMethods {
  fieldChanged?: EntryPoints.Client.fieldChanged;
  pageInit?: EntryPoints.Client.pageInit;
  localizationContextEnter?: EntryPoints.Client.localizationContextEnter;
  localizationContextExit?: EntryPoints.Client.localizationContextExit;
  validateLine?: EntryPoints.Client.validateLine;
  validateInsert?: EntryPoints.Client.validateInsert;
  validateField?: EntryPoints.Client.validateField;
  validateDelete?: EntryPoints.Client.validateDelete;
  sublistChanged?: EntryPoints.Client.sublistChanged;
  saveRecord?: EntryPoints.Client.saveRecord;
  postSourcing?: EntryPoints.Client.postSourcing;
}

in a module

export const { pageInit } : clientMethods = { 
  pageInit : (context ) => {
    // todo
  }

The reason i do it is be catch simple typos on exported methods that are standard while encapsulating some of the typings to a central, repeatable spot.

If exporting anything that is not standard then I can add it as a union in the project's types.

I think it would be useful to have something like the above clientMethods included in this project. I can do a PR in a few weeks (think of this as a placeholder until then).

[ShawnTalbert]

At our firm, we start all scripts from exemplar templates which serve a similar purpose.

It's worth discussing; should this types library expand beyond describing just the API of individual modules and provide additional guidance on typing for top level scripts?

[MrRob]

Hmm, I'm not sure. I kind of think maybe that sort of thing should live in a separate module. But we could include tips / guidance in the ReadMe, or other documentation