Skip to content

Type-level test coverage: @ngrx/store-devtools #175

Description

@Terrence721

Sub-issue of #162 (strengthen type-level test coverage to catch declared-vs-actual type mismatches, all modules).

Apply the two practices from #162 to store-devtools's spec/types/** tests:

  • Cover every exported field/selector/action-creator, not a representative subset.
  • Import through the real package name (@ngrx/store-devtools) wherever practical when asserting something about the module's public API surface, not an internal src/... path.

Deferred — do not start until the store-devtools module's own code-review pass under #32 is either in progress or complete, so this work happens with that module's public API surface already freshly understood.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    Status
    Planned

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions