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

fixed bold name error in some templates #20

Merged
merged 8 commits into from
Jun 5, 2017
Merged

Conversation

avirlrma
Copy link
Contributor

@avirlrma avirlrma commented Jun 5, 2017

#19 Fixed the issue!
Change was required in templates 2,4,6.I also removed some extra code.
So earlier in template 2,4,6, "Richard P. Hendricks" looked like "Richard P. Hendricks" now it should look like "Richard P. Hendricks"
Could you @saadq test and merge this?
BTW You were really helpful, made my work so much easier considering the fact that this was my first good PR.
Thanks!

Copy link
Owner

@saadq saadq left a comment

Choose a reason for hiding this comment

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

Nice work! Thanks for your contribution.

Before I can accept this pull request, there are a few things to take note of:

  1. You have some duplicate files committed. It seems for each template, you have a duplicate index.js file. Just be sure to remove that from the commit.

  2. Your indentation/whitespace has some issues. Just make sure to run npm run lint to figure out what you should change. npm run fix will automatically fix some of the issues for you. npm run format will automatically keep the formatting of the code consistent.

When you are all done with these changes, make sure to run npm test to make sure everything is working right. Just be sure to stop the server if it's running in order to allow the test to work, otherwise there might be issues when it tries to start its own server.

nameEnd = names[names.length - 1]
} else {
nameStart = names[0]
nameEnd = names.slice(1,names.length).join(' ')
}
Copy link
Owner

Choose a reason for hiding this comment

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

Indentation is a bit messed up here, and I believe it might be because you're using a tab somewhere. The project is using 2-space indent.

`
}

module.exports = template2
Copy link
Owner

Choose a reason for hiding this comment

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

This file shouldn't exist.

nameStart = names.slice(0, names.length - 1).join(' ')
nameEnd = names[names.length - 1]
nameStart = names[0]
nameEnd = names.slice(1,names.length).join(' ')
}
}

Copy link
Owner

Choose a reason for hiding this comment

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

LGTM

`
}

module.exports = template4
Copy link
Owner

Choose a reason for hiding this comment

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

This file also shouldn't be committed.

nameStart = names.slice(0, names.length - 1).join(' ')
nameEnd = names[names.length - 1]
nameStart = names[0]
nameEnd = names.slice(1,names.length).join(' ')
}
}

Copy link
Owner

Choose a reason for hiding this comment

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

Same as before, just make sure the indentation/whitespace is consistent with the project.

`
}

module.exports = template6
Copy link
Owner

Choose a reason for hiding this comment

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

Just remove this file as well!

@avirlrma
Copy link
Contributor Author

avirlrma commented Jun 5, 2017

I guess I did the neccesary things. Sorry for the indentation thing, I am in habit of tabs.I'm not sure about the npm thing.So please review the changes and merge it if it's all good.

@saadq
Copy link
Owner

saadq commented Jun 5, 2017

Are you unfamiliar with running npm scripts? Do you have node and npm installed? You can run:

$ npm run lint

in the command line, and it will tell you about any formatting/linting errors. I had listed a few of them although there are a couple more. Rather than listing them all in a review, could you just run npm run lint in the command line so it will list all of the small minor formatting issues you could fix. Let me know if you need further assistance.

Edit: I've actually posted a second review below, so it isn't necessary for you to run the npm scripts yourself although it would be good practice in case you ever want to contribute to a node project again.

nameStart = names.slice(0, names.length - 1).join(' ')
nameEnd = names[names.length - 1]
nameStart = names[0]
nameEnd = names.slice(1,names.length).join(' ')
Copy link
Owner

Choose a reason for hiding this comment

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

nit: add a space after the comma. 1, names.length

nameStart = names.slice(0, names.length - 1).join(' ')
nameEnd = names[names.length - 1]
nameStart = names[0]
nameEnd = names.slice(1,names.length).join(' ')
Copy link
Owner

Choose a reason for hiding this comment

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

same as above.

nameStart = names.slice(0, names.length - 1).join(' ')
nameEnd = names[names.length - 1]
nameStart = names[0]
nameEnd = names.slice(1,names.length).join(' ')
Copy link
Owner

Choose a reason for hiding this comment

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

same!

@saadq
Copy link
Owner

saadq commented Jun 5, 2017

For simplicity, I've also posted the linting issues here in a new review. The project follows a pretty strict style guide, so little things like spacing will make the tests fail. It's usually pretty easy to fix if you use npm run fix in the command line to automatically fix linting issues or npm run format to automatically make style consistent. But if you don't have npm available, you can just fix those issues I just mentioned in the above review.

@avirlrma
Copy link
Contributor Author

avirlrma commented Jun 5, 2017

I guess it's all done?

@saadq saadq merged commit dd45110 into saadq:master Jun 5, 2017
@avirlrma
Copy link
Contributor Author

avirlrma commented Jun 5, 2017

@saadq Thanks man!
Learned a lot!
Sorry for trouble caused, I'm just a noob.
Would you mind If I work on more Issues?

@saadq
Copy link
Owner

saadq commented Jun 5, 2017

Hey @aviral1701, thanks again for the contribution! It's much appreciated. I would be glad to have some help on the issues, although I would definitely first recommend setting up your environment if you haven't already. By that I mean having node and npm installed so that you can run the app locally and have access to all the npm scripts like linting, testing, formatting, etc so that code reviews are a lot easier and we can focus on the code itself instead of trivial things like indentation and formatting.

I've already start working on #6, #7, and #8, and have some plans for #14, but if you have any interest in the other ones feel free to tackle them.

If you are interested in any of them just comment in the issue and I can provide whatever info (if any) I already have about the issue! :)

@saadq
Copy link
Owner

saadq commented Feb 5, 2018

@aviral1701 I just added you as a contributor to the README, let me know if you'd rather not be on there. Thanks your contribution :)

@avirlrma
Copy link
Contributor Author

avirlrma commented Feb 5, 2018

Hey @saadq. Thanks for adding me in the contributors. Your project was my first open source contribution,so thanks for that as well. See ya ;)

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