This blog post series has moved here.
You might also be interested in the 2016 version.
| --- | |
| #### | |
| #### THIS IS OLD AND OUTDATED | |
| #### LIKE, ANSIBLE 1.0 OLD. | |
| #### | |
| #### PROBABLY HIT UP https://docs.ansible.com MY DUDES | |
| #### | |
| #### IF IT BREAKS I'M JUST SOME GUY WITH | |
| #### A DOG, OK, SORRY | |
| #### |
This blog post series has moved here.
You might also be interested in the 2016 version.
| " ---------------------------------------------------------------------------- | |
| " vimawesome.com | |
| " ---------------------------------------------------------------------------- | |
| function! VimAwesomeComplete() abort | |
| let prefix = matchstr(strpart(getline('.'), 0, col('.') - 1), '[.a-zA-Z0-9_/-]*$') | |
| echohl WarningMsg | |
| echo 'Downloading plugin list from VimAwesome' | |
| echohl None | |
| ruby << EOF | |
| require 'json' |
In this gist I would like to describe an idea for GraphQL subscriptions. It was inspired by conversations about subscriptions in the GraphQL slack channel and different GH issues, like #89 and #411.
At the moment GraphQL allows 2 types of queries:
querymutationReference implementation also adds the third type: subscription. It does not have any semantics yet, so here I would like to propose one possible semantics interpretation and the reasoning behind it.