Skip to content

[WIP] Docstring review #329

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

Merged
merged 11 commits into from
Jan 17, 2016
Merged

Conversation

BibMartin
Copy link
Contributor

Starting to address #140
Hunting TODO with grep -r TODO

@ocefpaf
Copy link
Member

ocefpaf commented Jan 15, 2016

@andrewgiessel Can I recruit you to review these? (As the only native English speaker I guess you are the most qualified to review docstrings 😝)

@ocefpaf ocefpaf added the documentation Documentation about a certain topic should be added label Jan 15, 2016
@ocefpaf ocefpaf added this to the v0.2.0 milestone Jan 15, 2016
The HTML data to be embedded.
width : int or str, default '100%'
The width of the output div.
Ex : 120 , '120px', '80%'
Copy link
Member

Choose a reason for hiding this comment

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

We can drop the space between Ex and :

@BibMartin
Copy link
Contributor Author

(suggestion + I agree) = correction

@BibMartin BibMartin mentioned this pull request Jan 15, 2016
@BibMartin
Copy link
Contributor Author

@ocefpaf
At the cost of being here ; I would like to drop features.ColorScale object in favor of colormap.ColorMap, so that we don't have to handle future deprecation warnings.

What do you think ? Can I do it in this PR, or wait for it to be merged and do another one ?

@BibMartin
Copy link
Contributor Author

Same question about fixing #247

@ocefpaf
Copy link
Member

ocefpaf commented Jan 16, 2016

Do what is most convenient. I am OK with a mixed porpuse PR.
On Jan 16, 2016 8:08 AM, "Martin Journois" [email protected] wrote:

Same question about fixing #247
#247


Reply to this email directly or view it on GitHub
#329 (comment)
.

@BibMartin
Copy link
Contributor Author

✅ I think I'm done for this PR.
@ocefpaf Please tell me if you want I squash, if you're okay with all this mess.

@ocefpaf
Copy link
Member

ocefpaf commented Jan 16, 2016

✅ I think I'm done for this PR.

Thanks! I will take a second look and merge it.

@ocefpaf Please tell me if you want I squash, if you're okay with all this mess.

Let's not squash this one in case we need to reference a certain commit later.

@ocefpaf
Copy link
Member

ocefpaf commented Jan 16, 2016

A few extra minor comments and I am done. (BTW. I am OK with the docstings as is and I can merge without the suggestions if you do not want to change.)

@BibMartin
Copy link
Contributor Author

Finally I removed the title to keep it simple.

If you're okay, it's ready to go.

@ocefpaf
Copy link
Member

ocefpaf commented Jan 17, 2016

Awesome!

ocefpaf added a commit that referenced this pull request Jan 17, 2016
@ocefpaf ocefpaf merged commit e29bfd9 into python-visualization:master Jan 17, 2016
@ocefpaf ocefpaf added the bug An issue describing unexpected or malicious behaviour label Feb 12, 2016
sanga pushed a commit to sanga/folium that referenced this pull request Oct 24, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug An issue describing unexpected or malicious behaviour documentation Documentation about a certain topic should be added
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants