feature request Office-Addin-Mock support CustomFunctions.Error

[mcshaz]

In an excel custom functions add in, I have to add a CustomFunctions.Error function to the global scope before running tests. I am using the following code (which I am not suggesting is sufficient to cover the use cases for the broad range of users) which gives a brief outline of another module which could be useful if added to the Office-Addin-Mock package:

enum ErrorCode {
  invalidValue = "#VALUE!",
  notAvailable = "#N/A",
  divisionByZero = "#DIV/0!",
  invalidNumber = "#NUM!",
  nullReference = "#NULL!",
  invalidName = "#NAME?",
  invalidReference = "#REF!",
}

class CustomFunctionError extends Error {
  constructor(readonly code: ErrorCode, message?: string) {
    super(message);
  }
}

const CustomFunctions = {
  Error: CustomFunctionError,
  ErrorCode: ErrorCode,
  associate: () => undefined,
};

and it is used something like (mocha/chai):

describe("myFunction", function () {
  global.CustomFunctions = CustomFunctions;
  it("throws an error when the string argument is empty", function () {
    expect(() => myFunction("", [[["a"]]])).to.throw(/require/i);
'''

[rhdhvolschenk]

The office-addin-mock package does not provide one of the available enums in the Office namespace.
This means that each one you use in code has to be mocked before being able to run tests. Silly.