825: null pointer exception new cronjob dialog suggest cronjob name #856
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
andrewbess
approved these changes
Dec 17, 2021
There was a problem hiding this comment.
Hello @bohdan-harniuk
Thank you for your contribution
Approved ✔️
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description (*)
Fixed java.lang.NullPointerException when opening new cron job dialog for an invalid Magento 2 module.
The bug was reproduced before fixing it:
Behaviour after bug fixing (for an invalid module structure):
The cron job name is not auto-populated as it cannot be resolved without valid module structure.
Behaviour after bug fixing (for a valid module structure):
The cron job name is auto-populated.
Fixed Issues (if relevant)
Contribution checklist (*)