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(devkit): run callback for forEachProjectConfig when target.options is undefined #23143

Merged
merged 1 commit into from
May 2, 2024

Conversation

Coly010
Copy link
Contributor

@Coly010 Coly010 commented May 2, 2024

Current Behavior

forEachExecutorOptions will not run the callback if target.options is undefined.
This means that even if a target exists with an executor, the target is not being processed if it does not have options.

Expected Behavior

Run the callback anyway even if target.options is undefined

Related Issue(s)

Fixes #

@Coly010 Coly010 requested a review from a team as a code owner May 2, 2024 14:06
@Coly010 Coly010 requested a review from AgentEnder May 2, 2024 14:06
@Coly010 Coly010 self-assigned this May 2, 2024
Copy link

vercel bot commented May 2, 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 May 2, 2024 2:28pm

@Coly010 Coly010 force-pushed the for-each-executors-options-cb branch from 87ea064 to d4285c6 Compare May 2, 2024 14:26
@Coly010 Coly010 requested a review from a team as a code owner May 2, 2024 14:26
@Coly010 Coly010 requested a review from leosvelperez May 2, 2024 14:26
@JamesHenry JamesHenry changed the title feat(devkit): run callback for forEachProjectConfig when target.options is undefined fix(devkit): run callback for forEachProjectConfig when target.options is undefined May 2, 2024
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 May 11, 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.

None yet

3 participants