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

Un-Feature Request: Remove ability to edit after translation or kata fork has been approved #3280

Open
FranzMartyn opened this issue Sep 17, 2024 · 1 comment

Comments

@FranzMartyn
Copy link

FranzMartyn commented Sep 17, 2024

The origin of this Issue stems from my Groovy translation of The Office II - Boredom Score. After my first Groovy translation of this Kata got approved, I found an error in the random tests. Where the problem starts to arise, is that I decided to directly edit the translation instead of creating a fork to fix the issue. This resulted in the fixed version being displayed when clicking on the translation, but the old version being used when actually solving the Kata in Groovy. I only found out about it after the user B1ts pointed it out to me.

I would also ask to update concepts/kata/translations and curation/guidelines/translation of the codewars documentation and perhaps even the (?) Help part of the code runner for translations. Since I have only found a slight hint of having to fork the translation for fixing issues etc. in concepts/kata/translations

image

@hobovsky
Copy link

hobovsky commented Sep 17, 2024

The paragraph you highlighted is related to something else, outdated and not valid anymore. You are right that docs do not explain that editing an approved or rejected fork has no effect, but this should be in general disabled instead of documented.

@FranzMartyn FranzMartyn changed the title Un-Feature Request: Remove ability to edit after translationed has been approved Un-Feature Request: Remove ability to edit after translation or kata fork has been approved Sep 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants