-
Notifications
You must be signed in to change notification settings - Fork 34
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
offshoot gen_test_data() from very long generate_data() #15
Conversation
Thank you for posting the PR to this repo! The changes look good, though it would make my life a little easier if I hold off on merging it until I can remove the original code from |
Thanks for the updates. The changes look good, though it's highlighting the lack of integration testing in this repo. I'm going to look into that now. |
I got an e2e workflow enabled on this repo in #33. I'm going to rebase this PR to trigger it to run. |
@Mergifyio rebase |
Function generate_data() is huge and messy. Refactor it. Move code around `json.dump` to gen_test_data() because it is under loop `for instruction_data_entry in instruction_data` by accidentally. Code is just moved, without internal changes. Signed-off-by: Costa Shulyupin <costa.shul@redhat.com>
Function generate_data() is huge and messy. Refactor it. Signed-off-by: Costa Shulyupin <costa.shul@redhat.com>
✅ Branch has been successfully rebased |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, and the e2e test workflow passed
Function generate_data is huge and messy.
Refactor it.