Summary

Allow us to define empty interfaces for extends.

Review Request #14680 — Created Nov. 8, 2025 and submitted Dec. 5, 2025, 9:39 a.m.

Information

Owner

david

Repository

beanbag-eslint-plugin

Branch

master

Bugs

Depends On

Reviewers

Groups

beanbag-misc

People

Description

For some of our attributes definitions with inherited models/views, it
can be handy to define an empty interface that extends the base class
one. This change enables that for our linting rules.

I've also alphabetized the rules in this definition in case it expands
further.

Testing Done

Set up a test case where we defined an interface that did nothing but
extend a base interface, and saw that I no longer got errors about it
from eslint.

Commits

Summary	ID
Allow us to define empty interfaces for extends. For some of our attributes definitions with inherited models/views, it can be handy to define an empty interface that extends the base class one. This change enables that for our linting rules. Testing Done: Set up a test case where we defined an interface that did nothing but extend a base interface, and saw that I no longer got errors about it from eslint.	tywzyzsquzrrmzqmvvlznxopvwpolnsx

Summary

Allow us to define empty interfaces for extends.

For some of our attributes definitions with inherited models/views, it can be handy to define an empty interface that extends the base class one. This change enables that for our linting rules. Testing Done: Set up a test case where we defined an interface that did nothing but extend a base interface, and saw that I no longer got errors about it from eslint.

tywzyzsquzrrmzqmvvlznxopvwpolnsx

flake8 passed.

JSHint passed.

Ship it!

```
Ship It!
```

Status:: Completed
Change Summary:: Pushed to master (8e20ceb)