-
-
Notifications
You must be signed in to change notification settings - Fork 158
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
Example files naming and Xcode Project #42
Comments
Maybe it was a little late last night for me. Would these be valid "example" file names? BobExample.swift |
@masters3d, this is a great idea. Being able to name the tests BobTest.swift, the example BobExample.swift and the user's solution Bob.swift would really simplify things. It would not only make it easier to maintain the problem sets, but it would streamline the user's process. Instead of creating a new project for each exercise, they could just use the same project and add new exercises as they go. If the restriction is that the examples must have /[Ee]xample/ in them, then BobExample.swift should work. That regex isn't anchored, so it should be okay. Let's get confirmation from @kytrinyx, then rename the existing example files. |
@masters3d Yepp, Would this structure the repo differently? |
no, only the |
Thank you! renaming done. |
exercism/ruby#102
"The only restriction is that the example file needs to have /[Ee]xample/ in the name" - @kytrinyx
I want to understand why the test files can be different names but the examples files names need to be "/[Ee]xample/ ". In an xcode project I can't have the same filename for different files in the same project because the project wont compile. Having all the problems in one project would allow faster updates of language changes ( 1.x to 1.x+ ) and in the future Travis integration.
http://docs.travis-ci.com/user/osx-ci-environment/
http://docs.travis-ci.com/user/languages/objective-c/
exercism/exercism#316
The text was updated successfully, but these errors were encountered: