Skip to content

1.4.0 release notes name nonexistent unknown-member-type diagnostic #5284

Open

Description

@adamtheturtle

Describe the Bug

The Pyrefly 1.4.0 release notes refer to unknown-member-type in two places:

  • Release Highlights → Type Checking → New opt-in checks for untyped code.
  • New & Improved → Error Reporting → the entry describing attribute accesses whose type is unknown.

However, the released 1.4.0 binary rejects that diagnostic name. The corresponding diagnostic is named unknown-attribute-access in the 1.4.0 error definitions.

To reproduce, create example.py containing:

def get_value(item):
    return item.value

Run:

$ uvx --from pyrefly==1.4.0 pyrefly check --error unknown-member-type example.py
error: invalid value 'unknown-member-type' for '--error <ERROR>'

Using --error unknown-attribute-access instead is accepted and reports the attribute access under [unknown-attribute-access].

Could both release-note references be updated to unknown-attribute-access, so readers can enable the check using the documented name?

Activity

  1. self-assigned this
    on Oct 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

language-serverIssues specific to our IDE integration rather than type checking

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions