Corey Farwell

Thanks for the bug report! 🐛

> Does this mean however that all validations are in effect not working as an empty string is returned every time? From what I can tell, we return an empty...

Sounds good to me, though we'll need to do a major version bump for this, which is fine

> Why not just having arbitrary fields (stored as an associative array) and being able to access them through a normal getter function? Sounds good > That way, the second...

Here are some helpful resources - [Retrieving browser 2D positions from THREE Geometries](http://zachberry.com/blog/tracking-3d-objects-in-2d-with-three-js/) - [Label placement algorithms](https://en.wikipedia.org/wiki/Automatic_label_placement) - [Examples of sprite text labels using THREE.js](https://stemkoski.github.io/Three.js/#sprite-text-labels)

I'm thinking my first pass at this will, I'll show all labels by default and won't bother trying to intelligently hide overlapping ones

Relevant blog post by MapBox https://www.mapbox.com/blog/placing-labels/

Absolutely, that sounds great! Feel free to open an pull request and I'd love to take a look :+1:

The line [here](https://github.com/frewsxcv/graphosaurus/blob/18e92235fd8bcc4e1e5880f50c66a7ebbcd1e5ac/src/frame.js#L203) might be problematic for your scenario. The distinction here is between [`THREE.Line`](http://threejs.org/docs/index.html#Reference/Objects/Line) and [`THREE.LineSegments`](http://threejs.org/docs/index.html#Reference/Objects/LineSegments). I originally used `THREE.Line`, but was encountering performance issues, and (if I recall...

Very basic event handling. You can see the `hover` and `click` properties on `Graph` here: https://cdn.rawgit.com/frewsxcv/graphosaurus/master/doc/Graph.html That was implemented in: https://github.com/frewsxcv/graphosaurus/pull/60 There are no events implemented for edges yet, but...