-
-
Notifications
You must be signed in to change notification settings - Fork 540
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
Clarification for canonical-data.json #1070
Comments
|
The few follow-up questions I have:
|
You do not need to follow the property as named in the specs, but I'd recommend it. By having the same name through all tracks we make it easier for polyglots to redo an exercise in another language, also it's easier to reason about implementations as maintainers. The name should be changed to follow the languages idioms and possibly syntax (hypothetically we could have languages which require names in all caps). But how ever you name your stuff if you not follow the property, please make sure that cases in the canonical data refering to the same property are using the same name in your implementation. Also make sure that different property names in the data should map to different things under test in your implementation. |
Thank you for your clarifications. |
After looking through the discussion about the new
canonical-data.json
format and what each property means I still have some thing I don't understand, I hope that somebody is willing to clarify that for me.What is
property
referring to, my understanding is that is the method where the exercise solution is supposed to be?Ex (Ruby):
Implementation
Test
If my understanding is correct I have a few follow up questions.
The text was updated successfully, but these errors were encountered: