Skip to content

Obsolete conformance#55

Open
AryaHassanli wants to merge 3 commits intomainfrom
obsolete-conformance
Open

Obsolete conformance#55
AryaHassanli wants to merge 3 commits intomainfrom
obsolete-conformance

Conversation

@AryaHassanli
Copy link
Copy Markdown
Contributor

No description provided.

@AryaHassanli AryaHassanli requested a review from a team as a code owner March 31, 2026 18:33
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces support for "Obsolete" (Z) conformance, including grammar updates to the PEG parser, new data structures, and integration into XML rendering and parsing. A review comment suggests that the evaluation of obsolete elements should result in a disallowed state rather than a deprecated state to strictly adhere to the Matter specification.

Comment on lines +23 to +25
func (d *Obsolete) Eval(context Context) (ConformanceState, error) {
return ConformanceState{State: StateDeprecated, Confidence: ConfidenceDefinite}, nil
}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

In the Matter specification, 'Obsolete' (Z) conformance indicates that an element has been removed and SHALL NOT be used by implementations. This is a stricter requirement than 'Deprecated' (D), which still requires support for backward compatibility. Evaluating Obsolete to StateDeprecated may be incorrect if the intention is to strictly disallow these elements. Consider using StateDisallowed instead, to align with the 'SHALL NOT' requirement of the specification.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants