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

Issues with code in the read me #11

Closed
irr1449 opened this issue Apr 3, 2018 · 6 comments
Closed

Issues with code in the read me #11

irr1449 opened this issue Apr 3, 2018 · 6 comments

Comments

@irr1449
Copy link

irr1449 commented Apr 3, 2018

Under "Playing around with data"

The line

players = api.players().filter(players_names['epickitten'])

Should be player_names not players_names.

players = api.players().filter(player_names['epickitten'])

I would be more than happy to make fixes. Can I upload my own fixes to the repo?

@ramonsaraiva
Copy link
Owner

Hell yeah!

Please do it - whatever you want to contribute.
Open a Pull Request and i'll merge it if the changes make sense.

@ramonsaraiva
Copy link
Owner

If you've never done that before, here are some pretty good guides from GitHub https://help.github.com/categories/collaborating-with-issues-and-pull-requests/

@dandyrilla
Copy link
Contributor

dandyrilla commented Apr 4, 2018

I'm not sure, I think that you just omitted equal sign between player_names and ['epickitten']. I understood that .filter() method accepts only string which exists in FILTER_MAPPING.

## original
players = api.players().filter(player_names['epickitten'])

## suggested to fix
players = api.players().filter(player_names=['epickitten'])

@ramonsaraiva
Copy link
Owner

@dandyrilla I think there's still a typo in this section https://github.com/ramonsaraiva/pubg-python#playing-around-with-data - it says players_names and not player_names.

I'll give him a buffer to create a PR and fix that, if not i can fix it.

@dandyrilla
Copy link
Contributor

@ramonsaraiva
I'm very impressed by your quick response. Thank you for taking account into my suggestion. Yeah, let's wait for his PR.

@ramonsaraiva
Copy link
Owner

Fixed.

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

No branches or pull requests

3 participants