Skip to content

Revert "fix: make composeDirective argument non-nullable"#3281

Merged
dariuszkuc merged 1 commit intomainfrom
revert-3278-compose_directive_fix
Jun 25, 2025
Merged

Revert "fix: make composeDirective argument non-nullable"#3281
dariuszkuc merged 1 commit intomainfrom
revert-3278-compose_directive_fix

Conversation

@dariuszkuc
Copy link
Member

Reverts #3278

@changeset-bot
Copy link

changeset-bot bot commented Jun 25, 2025

⚠️ No Changeset found

Latest commit: 83857a1

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@codesandbox-ci
Copy link

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

@dariuszkuc dariuszkuc marked this pull request as ready for review June 25, 2025 16:34
@dariuszkuc dariuszkuc requested a review from a team as a code owner June 25, 2025 16:34
@dariuszkuc dariuszkuc merged commit 5cf7c72 into main Jun 25, 2025
15 checks passed
@dariuszkuc dariuszkuc deleted the revert-3278-compose_directive_fix branch June 25, 2025 17:02
dariuszkuc added a commit that referenced this pull request Jun 25, 2025
Since we cannot easily fix incorrect directive definition (#3281) without breaking our clients. This PR improves error messages when `@composeDirective` arguments are NULL or empty strings.

Previous message on undefined/null argument value

`Cannot read properties of undefined (reading '0')`

New message

`Argument to @composeDirective in subgraph "${sg.name}" cannot be NULL or an empty String`
dariuszkuc added a commit that referenced this pull request Jun 25, 2025
Since we cannot easily fix incorrect directive definition
(#3281) without breaking
our clients. This PR improves error messages when `@composeDirective`
arguments are NULL or empty strings.

Previous message on undefined/null argument value

`Cannot read properties of undefined (reading '0')`

New message

`Argument to @composeDirective in subgraph "${sg.name}" cannot be NULL
or an empty String`
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