-
Notifications
You must be signed in to change notification settings - Fork 2
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
OpcodeName.java:37-39: Code duplication with... #75
Comments
@volodya-lombrozo can I take this one? |
@h1alexbel Sure, please, go ahead! This issue might be tricky, so don't hesitate to ask for help or explanation. |
@volodya-lombrozo is it closed by mistake? The puzzle still in the source code |
@volodya-lombrozo my bad actually. Looks like I referenced in pull request description here: objectionary/jeo-maven-plugin#771 (comment). We should reopen this |
@volodya-lombrozo after we released |
@h1alexbel Oh, sorry, I missed that as well. Reopen it. |
@h1alexbel We significantly changed the |
@h1alexbel you can track the progress here. |
@volodya-lombrozo got it |
@0pdd Hey there, awesome job on that enhancement suggestion! 🎉 You've just snagged yourself 8 bonus points - that's our team policy for accepted enhancements. Keep those great ideas coming! And hey, if you spot anything in the repo that doesn't look quite right, don't hold back - report those bugs too. Your keen eye helps us all improve! |
I see you're talking to me, but I can't reply since I'm not a chat bot. |
1 similar comment
I see you're talking to me, but I can't reply since I'm not a chat bot. |
The puzzle
65-ca6c046e
from #65 has to be resolved:opeo-maven-plugin/src/main/java/org/eolang/opeo/ast/OpcodeName.java
Lines 37 to 39 in 0008217
The puzzle was created by @rultor on 15-Jan-24.
Estimate: 30 minutes, role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.
The text was updated successfully, but these errors were encountered: