I think both of those things are good suggestions. Documentation is certainly lacking.

Adding the additional option should be fairly easy. This might be an argument to change our allowStandaloneDeclarations to allowDeclarations and match whatever functionality that package exposes.

I'll work on this stuff and close / comment this issue when I have something.

@TristonJ @snebjorn any update on this ? :)

@TristonJ @snebjorn Any updates?

@TristonJ I see that there's PR that should add this option. Can it be merged soon?

For now I have an override in Angular that disables on classProperties in certain files

{
  // See no-restricted-syntax
  "files": ["*[.-]component.ts", "*[.-]interceptor.ts"],
  "rules": {
    // Angular hooks should be named functions
    // https://github.com/mojohaus/extra-enforcer-rules/issues/186
    "extra-rules/potential-point-free": "warn",
    "prefer-arrow/prefer-arrow-functions": [
      "error",
      {
        ...preferArrowFunctionsConfig,
        https://github.com/TristonJ/eslint-plugin-prefer-arrow/issues/17
        "classPropertiesAllowed": false,
      },
    ],
  },
},

But I would like to be able to tell this plugin to ignore:
intercept, ngOnChanges, ngOnInit, ngDoCheck, ngAfterContentInit, ngAfterContentChecked, ngAfterViewInit, ngAfterViewChecked, ngOnDestroy, ...