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

dot-dsl: implement exercise #732

Closed
ilya-khadykin opened this issue Oct 6, 2017 · 3 comments · Fixed by #978
Closed

dot-dsl: implement exercise #732

ilya-khadykin opened this issue Oct 6, 2017 · 3 comments · Fixed by #978

Comments

@ilya-khadykin
Copy link
Contributor

There are exercises that are not yet implemented in Python track (the full list of them - #417 (comment)).
You can help us change this situation by implementing this one. Ref #417

The guide "Implement an exercise from specification" will help you succeed.

If you still have questions, I encourage you to ask them before starting working on the issue.

I also suggest claiming the issue by creating an empty PR as stated here

Please note that there are some special 'closing issue' keywords that you can put in description of your PR and Github will take care of closing the corresponding issue automatically after merge.
This simple thing helps us a lot, and makes our life a bit easier

@ackerleytng
Copy link
Contributor

Okay, I think I'm pretty much done with implementing this exercise, but Travis says

$ ./bin/configlet lint .
-> An implementation for 'dot-dsl' was found, but config.json does not reference this exercise.

Where can I find information about config.json and how to fill it in?

Thanks!

@ackerleytng
Copy link
Contributor

Oh I found it! In case anyone else is looking for the reference, I found it here https://github.com/exercism/docs/blob/master/language-tracks/configuration/exercises.md

@ackerleytng
Copy link
Contributor

Ok, ready for review now!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants