-
-
Notifications
You must be signed in to change notification settings - Fork 157
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
Project structure for newcomers #121
Comments
Hey, thanks for the feedback! I can see how that could be confusing to newcomers. Would you be willing to submit a PR with "stub" solution files? I think that's a great idea. Update: WIP #122 |
Hello world was already added in exercism#122, add to next 4 exercises (to make it 5) Fixes exercism#121
Hey @tejasbubane @yurrriq Thanks for your work on this. |
@kevgathuku @tejasbubane @yurrriq I think making stub solution files mandatory for all tracks - esp. using "real-world" leiningen projects - is a must-have. On the xscheme and xelisp tracks we always provide stub files to make sure the exercist has the proper requires/includes and file format (esp. for elisp so flycheck doesn't have a conniption)... having a stub file with the ns macro declaration and any necessary requires makes complete sense. I'd be happy to create and self-assign an issue to take this on if desired. |
Sounds good to me then. |
I am pretty new the clojure and just submitted the
hello-world
. Therunning the tests
section on language page does not mention where to put my solution file, so initially I assumed it would be the problem directory itself. This gave me the error:So I finally put it inside
test/
assuming it is the tests that require the file and tests ran successfully. Later found out thatexercism-clojure
uses to the"real-world project structure"
here #84.I think the directory structure should be mentioned in
running the tests
section. Also if possible, creating an empty file insidesrc
directory would help, so that people know the source code goes there.The text was updated successfully, but these errors were encountered: