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.

Sign up for GitHub

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

Jump to bottom

Rename isochrones to reachability #83

Open
chrstnbwnkl opened this issue Nov 24, 2022 · 2 comments
Open

Rename isochrones to reachability #83

chrstnbwnkl opened this issue Nov 24, 2022 · 2 comments

Comments

@chrstnbwnkl
Copy link
Contributor

The isochrones method seems to be a bit of a misnomer, because in most cases, the isochrone endpoints can be used for isochrones and isodistances. Something like reachability could be a better suited name, what do you think? We just released 1.0.0 a couple months ago, so maybe something for down the road.
@nilsnolde
Copy link
Owner

Jep, agree, reachability is better! But definitely a major version sort of thing

@nilsnolde nilsnolde added the v2 label Nov 24, 2022
@nilsnolde
Copy link
Owner

ah well, maybe not.. I guess we could support both for a while and add a deprecation label/notice. even though the Isochrone(s) objects are also "public" API, I wouldn't have a hard time renaming them to Reachabilit-ies/y..

@nilsnolde nilsnolde removed the v2 label Dec 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nilsnolde @chrstnbwnkl