-
-
Notifications
You must be signed in to change notification settings - Fork 659
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
pangram: clarify language in README #802
Conversation
Made README clearer in regards to allowed inputs for pangram / allowed inputs for interface. Added the term 'rune' into the problem context. Resolves #801
I'm not fully up on generating the READMEs, is this in danger of being overwritten? |
I don't think so, I believe that was a one time thing? I do have to look into it more, it's part of the reason why #786 has been sitting around. If that ends up happening we can redo in the local metafile or wherever. |
Yes, it would be overwritten but by us via configlet, automation in README's is a thing of the past. See the comment in 4a9e2a0. Full docs here. |
Okay, yeah, unless we change the description.md in the |
This may be a good example of why we moved to locally generated READMEs in the first place. |
I wonder if we're addressing the wrong problem here. Looking at exercism/problem-specifications@ff2abe7 & exercism/problem-specifications#842 it may be that we should update the test suite to reflect the |
Yeah, I think that is better since we are the divergent track here. |
Okay, do you want to update the |
I was gonna yank those two entries out of the test suite? |
Sounds good 👍 |
Made README clearer in regards to allowed inputs for pangram / allowed
inputs for interface.
Added the term 'rune' into the problem context.
Resolves #801