Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(core): ensure tuple passed to aggregate create nodes error #26456

Merged
merged 1 commit into from
Jun 7, 2024

Conversation

AgentEnder
Copy link
Member

Current Behavior

We throw an invalid aggregate create nodes error if a plugin hard-fails

Expected Behavior

All aggregate create nodes errors are Array

Related Issue(s)

Fixes #

@AgentEnder AgentEnder requested a review from a team as a code owner June 7, 2024 16:30
@AgentEnder AgentEnder requested a review from FrozenPandaz June 7, 2024 16:30
Copy link

vercel bot commented Jun 7, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment
Name Status Preview Updated (UTC)
nx-dev ⬜️ Ignored (Inspect) Visit Preview Jun 7, 2024 5:31pm

@@ -226,6 +226,11 @@ export class AggregateCreateNodesError extends Error {
) {
super('Failed to create nodes');
this.name = this.constructor.name;
if (!Array.isArray(errors) || (errors.length && errors[0].length !== 2)) {
Copy link
Collaborator

@FrozenPandaz FrozenPandaz Jun 7, 2024

Choose a reason for hiding this comment

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

I think we should check more than the first element. 🤷 I don't see an reason why not?

@AgentEnder AgentEnder enabled auto-merge (squash) June 7, 2024 18:07
@AgentEnder AgentEnder merged commit 8891bdc into master Jun 7, 2024
6 checks passed
@AgentEnder AgentEnder deleted the fix/plugin-error-handling-destructure-null branch June 7, 2024 18:14
Copy link

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 14, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants