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

Update documentation for pointFeature. #858

Merged
merged 3 commits into from
Jul 12, 2018
Merged

Update documentation for pointFeature. #858

merged 3 commits into from
Jul 12, 2018

Conversation

manthey
Copy link
Contributor

@manthey manthey commented Jul 2, 2018

This also touches documentation on util/clustering.js, though that could use some refactoring so that clusters are computed in map gcs rather than in feature gcs (usually interface gcs) and the cluster size is given in simpler units (such as display pixels).

This fixes a number of trivial documentation issues in other files, too.

@manthey manthey force-pushed the update-point-docs branch 2 times, most recently from 29c3596 to 306b12d Compare July 9, 2018 17:19
/**
* Set style(s) from array(s). For each style, the array should have one
* value per data item. The values are not converted or validated. Color
* values should be {@link geo.geoColorObject}s. If invalid values are given
Copy link
Member

Choose a reason for hiding this comment

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

is "s" after the "}" intentional?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes. It makes the docs read 'Color values should be geo.geoColorObjects.', which seemed more grammatical, but I'm not committed to the 's'.

Copy link
Member

Choose a reason for hiding this comment

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

I am fine with this. You could have said that 'Color' values should a a geo.geoColorObject.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I reworded it a little.

* @property {number} [width=256]
* @property {number} [height=256]
*/
// TODO: refactor point clustering to (a) not be based on window size, (b) use
Copy link
Member

Choose a reason for hiding this comment

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

perhaps we could create an issue for this and remove it from here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sure.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Apparently I already did (see issue #853). Do you want it removed? It stands as a warning to anyone using point clustering.

Copy link
Member

Choose a reason for hiding this comment

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

I would remove it as it is not consistent and a user would not dig in the code as much I think.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done.

manthey added 2 commits July 12, 2018 16:00
This also touches documentation on util/clustering.js, though that could
use some refactoring so that clusters are computed in map gcs rather
than in feature gcs (usually interface gcs) and the cluster size is
given in simpler units (such as display pixels).

This fixes a number of trivial documentation issues in other files, too.

Also, improve documentation of position in line and polygon features.
@manthey manthey force-pushed the update-point-docs branch from 306b12d to ad7646c Compare July 12, 2018 20:03
@manthey manthey merged commit dca5c39 into master Jul 12, 2018
@manthey manthey deleted the update-point-docs branch July 12, 2018 21:22
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