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

[5.x] Fix early return when no blueprint found & running in the console #323

Merged
merged 1 commit into from
Sep 10, 2023

Conversation

duncanmcclean
Copy link
Member

This pull request fixes an error caused by #320, where an early return with no value was causing havoc with the way ->mapWithKeys() works.

Fixes #322

@duncanmcclean duncanmcclean changed the title Fix early return when no blueprint found & running in the console [5.x] Fix early return when no blueprint found & running in the console Sep 10, 2023
@duncanmcclean duncanmcclean merged commit 05b7943 into 5.x Sep 10, 2023
7 of 8 checks passed
@duncanmcclean duncanmcclean deleted the fix/no-blueprint-console-early-return branch September 10, 2023 14:58
@github-actions
Copy link

Released as part of v5.2.2.

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.

Runway update (seems to) causes: foreach() argument must be of type array|object, null given error
1 participant