Skip to content

fix(refs): improve spec-not-found error message for unexpected refs - #123

Merged
SVilgelm merged 1 commit into
mainfrom
fix/spec-not-found-clarify-error
Sep 6, 2025
Merged

SVilgelm merged 1 commit into
mainfrom
fix/spec-not-found-clarify-error

Conversation

@SVilgelm

@SVilgelm SVilgelm commented Sep 6, 2025

Copy link
Copy Markdown
Member

Clarify error text when resolving component references by including
both the unexpected component name and the full ref string. Previously
the message only reported the component value, which made debugging less
informative when refs contain paths or complex identifiers. This change
adds the component name and the original ref to the error so callers
can more easily identify malformed or unexpected references.

Clarify error text when resolving component references by including
both the unexpected component name and the full ref string. Previously
the message only reported the component value, which made debugging less
informative when refs contain paths or complex identifiers. This change
adds the component name and the original ref to the error so callers
can more easily identify malformed or unexpected references.
Copilot AI review requested due to automatic review settings September 6, 2025 04:37

Copilot AI left a comment

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.

Pull Request Overview

This PR improves error messages when resolving component references by making them more informative for debugging. When an unexpected component name is encountered during reference resolution, the error now includes both the component name and the full reference string.

  • Enhanced error message to include both the unexpected component name and the original ref string
  • Changed error text from "unexpected component" to "unexpected component name" for clarity

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

@SVilgelm
SVilgelm merged commit b9b00a4 into main Sep 6, 2025
@SVilgelm
SVilgelm deleted the fix/spec-not-found-clarify-error branch September 6, 2025 04:39
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

⌂ 换网址