Andrew Dassonville

Looks like this is because we're not taking into account the pagination. To deal with this, let's use the `open_issues` property from the repo API (https://api.github.com/repos/gitpoint/git-point). Note this will mean...

@SammyIsra Actually here's a fun trick: Make a request to `https://api.github.com/repos/gitpoint/git-point/issues?state=closed&per_page=1&page=1`. This shows us the most recently closed issue (or opened if `state=open`) from the repository, but that's not what...

For future GraphQL reference, here's how we'd get the first 3 issues on the repository screen, along with the total number of open/closed issues: ```GraphQL { repository(owner: "gitpoint", name: "git-point")...

I love GraphQL now :joy: This simplifies things _a ton_.

Awesome @housseindjirdeh! I have a `graphql` branch made where we can start working on this and merge it into master when we're satisfied :)

Also create a commit bumping the version number in the package.json (titled something like `chore(release): bump version to v1.2.3`) and tag that commit as the release.

Any updates on this issue? How can we refresh an organization's location?

I think following a mongoose-like approach would be good to make an easier transition for people who may have used mongoose in the past. ```ts function myPlugin(model) { model.pre('get', (query)...

> Looks like if we just do hooks those type of plugins won't be compatible. Mongoose's type plugins seem pretty straight-forward. [Here's](https://github.com/mongoosejs/mongoose-double/blob/master/lib/index.js) the source for the `mongoose-double` plugin -- I...

This is a feature I've needed a few times now, and I'm totally willing to tackle it if we can come up with a sane implementation. Mongoose uses the `object.prop`...