-
Notifications
You must be signed in to change notification settings - Fork 90
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
Add wp post meta clean-duplicates <id> <key>
command
#366
Conversation
wp post meta clean-duplicates <id> <key>
commandwp post meta clean-duplicates <id> <key>
command
wp post meta clean-duplicates <id> <key>
commandwp post meta clean-duplicates <id> <key>
command
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.
Great start! Left a few comments on the test conditions.
Need suggestions/corrections for labelling.
Not sure I follow... can you explain further?
Should we do the same for the user and term meta commands.?
I think we can hold off for now. Should an actual need arise in the future, it should be simple enough to abstract this out.
I mean command is So the word |
@BhargavBhandari90 Oh, I see. The message should be something like |
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.
Great work on this, @BhargavBhandari90 ! 🎉
I made a few more changes you might find useful to review ^
Overall, you've did a great job 😊
Thank You @danielbachhuber
Yep, I saw that. |
Great work on this! A minor thing: This PR messed up the formatting of the JSON files in the Behat tests. I'll get that cleaned up again in a subsequent PR. |
Fixes: #356
Need suggestions/corrections for labelling.
QUESTION: Should we do the same for the user and term meta commands.?