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

Needs Docs: New Geo Field #988

Closed
JedWatson opened this issue Feb 4, 2015 · 3 comments
Closed

Needs Docs: New Geo Field #988

JedWatson opened this issue Feb 4, 2015 · 3 comments
Assignees
@andrewlinfoot

Comments

@JedWatson
Copy link
Member

Need to document the new Geo field I created, as per #969

I'm also considering renaming it to GeoPoint but that shouldn't be a blocker. Will make a call before it gets released.
@BerkeleyTrue
Copy link
Contributor

+1 GeoPoint as this is what I have seen with other ODM/ORM's

@JedWatson
Copy link
Member Author

@BerkeleyTrue I was considering allowing different types of Geo data to be stored (points, paths, etc) but I actually think this would be more easily done with different field types. I'll rename it to GeoPoint now.

JedWatson added a commit that referenced this issue Feb 4, 2015
@JedWatson
Renaming Geo => GeoPoint as per #988
934e243
@estilles estilles changed the title Document new Geo Field Needs Docs: New Geo Field Feb 6, 2015
@andrewlinfoot andrewlinfoot mentioned this issue Apr 29, 2016
Open
@andrewlinfoot
Copy link
Contributor

We're closing all documentation requests to keep the issue tracker unpolluted. I've moved this request over to the documentation repo: keystonejs/keystonejs-site#101

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@andrewlinfoot andrewlinfoot

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@JedWatson @andrewlinfoot @BerkeleyTrue @mxstbr