Skip to content

Make isogram exercise JSON Schema compliant#686

Merged
rbasso merged 1 commit intoexercism:masterfrom
tejasbubane:isogram-json-schema
Mar 10, 2017
Merged

Make isogram exercise JSON Schema compliant#686
rbasso merged 1 commit intoexercism:masterfrom
tejasbubane:isogram-json-schema

Conversation

@tejasbubane
Copy link
Copy Markdown
Member

@tejasbubane tejasbubane commented Mar 10, 2017

Ref #625

@tejasbubane tejasbubane force-pushed the isogram-json-schema branch from 5f69b04 to f815088 Compare March 10, 2017 10:43
Copy link
Copy Markdown
Contributor

@rbasso rbasso left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You changed some things:

  • Nesting: You added a test group with a new description.
  • Comments: You added two comments.
  • Compliance: You added exercise, version and property.
  • Formatting: Everything was formatted accordingly.

The first two things do not really fit in the commit's title, but they seems to be ok.

The choice of property's name was great! 👍

The forth one could also be a separated commit. This would make a better history and also make reviewing a little easier.

ps: I didn't checked if the test's contents match the original.

@tejasbubane
Copy link
Copy Markdown
Member Author

@rbasso Do you mean I should split the nesting and comments part from compliance?

@rbasso
Copy link
Copy Markdown
Contributor

rbasso commented Mar 10, 2017

You don't have to. This is ready to be merged. 👍

It was just a recommendation for future PRs, to consider splitting different things in different commits/PRs.

@rbasso rbasso merged commit 1722e46 into exercism:master Mar 10, 2017
@tejasbubane tejasbubane deleted the isogram-json-schema branch March 10, 2017 13:22
emcoding pushed a commit that referenced this pull request Nov 19, 2018
Remove instructions for direct test execution.
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 this pull request may close these issues.

2 participants